include/drivers/marvell/mochi: add detection of secure modeChange-Id: I99afc312617df86ae68eb30302203a03877ca748Signed-off-by: Konstantin Porotchkin <kostap@marvell.com>Reviewed-on: https://sj1git
include/drivers/marvell/mochi: add detection of secure modeChange-Id: I99afc312617df86ae68eb30302203a03877ca748Signed-off-by: Konstantin Porotchkin <kostap@marvell.com>Reviewed-on: https://sj1git1.cavium.com/22541Reviewed-by: Stefan Chulski <stefanc@marvell.com>Reviewed-by: Grzegorz Jaszczyk <jaszczyk@marvell.com>Tested-by: sa_ip-sw-jenkins <sa_ip-sw-jenkins@marvell.com>
show more ...
plat: marvell: t9130: pass actual CP count for load_imageAdd CN913x case to bl2_plat_get_cp_count.Fix loading of cp1/2 image. This is a preparationpatch for adding CN913x SoC family support.Cha
plat: marvell: t9130: pass actual CP count for load_imageAdd CN913x case to bl2_plat_get_cp_count.Fix loading of cp1/2 image. This is a preparationpatch for adding CN913x SoC family support.Change-Id: Id84a30203d20572fc0dfd3f91ea395c199a85fe9Signed-off-by: Ben Peled <bpeled@marvell.com>
plat: marvell: ap807: update configuration space of each CPBy default all external CPs start with configuration address space set to0xf200_0000. To overcome this issue, go in the loop and initiali
plat: marvell: ap807: update configuration space of each CPBy default all external CPs start with configuration address space set to0xf200_0000. To overcome this issue, go in the loop and initialize theCP one by one, using temporary window configuration which allows to accesseach CP and update its configuration space according to decodingwindows scheme defined for each platform.In case of cn9130 after this procedure bellow addresses will be used:CP0 - f2000000CP1 - f4000000CP2 - f6000000When the re-configuration is done there is need to restore previousdecoding window configuration(init_io_win).Change-Id: I1a652bfbd0bf7106930a7a4e949094dc9078a981Signed-off-by: Grzegorz Jaszczyk <jaz@semihalf.com>
plat: marvell: armada: add support for loading MG CM3 imagesIn order to access MG SRAM, the amb bridge needs to be configured which isdone in bl2 platform init.For MG CM3, the image is only load
plat: marvell: armada: add support for loading MG CM3 imagesIn order to access MG SRAM, the amb bridge needs to be configured which isdone in bl2 platform init.For MG CM3, the image is only loaded to its SRAM and the CM3 itself isleft in reset. It is because the next stage bootloader (e.g. u-boot)will trigger action which will take it out of reset when needed. Thiscan happen e.g. when appropriate device-tree setup (which has enabled802.3 auto-neg) will be chosen. In other cases the MG CM3 should not berunning.Change-Id: I816ea14e3a7174eace068ec44e3cc09998d0337eSigned-off-by: Grzegorz Jaszczyk <jaz@semihalf.com>
Sanitise includes across codebaseEnforce full include path for includes. Deprecate old paths.The following folders inside include/lib have been left unchanged:- include/lib/cpus/${ARCH}- inclu
Sanitise includes across codebaseEnforce full include path for includes. Deprecate old paths.The following folders inside include/lib have been left unchanged:- include/lib/cpus/${ARCH}- include/lib/el3_runtime/${ARCH}The reason for this change is that having a global namespace forincludes isn't a good idea. It defeats one of the advantages of havingfolders and it introduces problems that are sometimes subtle (becauseyou may not know the header you are actually including if there are twoof them).For example, this patch had to be created because two headers werecalled the same way: e0ea0928d5b7 ("Fix gpio includes of mt8173 platformto avoid collision."). More recently, this patch has had similarproblems: 46f9b2c3a282 ("drivers: add tzc380 support").This problem was introduced in commit 4ecca33988b9 ("Move include andsource files to logical locations"). At that time, there weren't toomany headers so it wasn't a real issue. However, time has shown thatthis creates problems.Platforms that want to preserve the way they include headers may add theremoved paths to PLAT_INCLUDES, but this is discouraged.Change-Id: I39dc53ed98f9e297a5966e723d1936d6ccf2fc8fSigned-off-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>
Standardise header guards across codebaseAll identifiers, regardless of use, that start with two underscores arereserved. This means they can't be used in header guards.The style that this proje
Standardise header guards across codebaseAll identifiers, regardless of use, that start with two underscores arereserved. This means they can't be used in header guards.The style that this project is now to use the full name of the file incapital letters followed by 'H'. For example, for a file called"uart_example.h", the header guard is UART_EXAMPLE_H.The exceptions are files that are imported from other projects:- CryptoCell driver- dt-bindings folders- zlib headersChange-Id: I50561bf6c88b491ec440d0c8385c74650f3c106eSigned-off-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>
plat: svc: ap807: add SVC configuration for AP807- add svc configuration according to values burnt to the chip efuseChange-Id: Icf5d7cc41bc09ac2244d0a126106e681afebb064Signed-off-by: Christine
plat: svc: ap807: add SVC configuration for AP807- add svc configuration according to values burnt to the chip efuseChange-Id: Icf5d7cc41bc09ac2244d0a126106e681afebb064Signed-off-by: Christine Gharzuzi <chrisg@marvell.com>Reviewed-by: Kostya Porotchkin <kostap@marvell.com>
marvell: drivers: Add MoChi driversAdd ModularChip and MCI drivers for A8K SoC family.ModularChip drivers include support for the internal buildingblocks of Marvell ARMADA SoCs - APN806, APN807 a
marvell: drivers: Add MoChi driversAdd ModularChip and MCI drivers for A8K SoC family.ModularChip drivers include support for the internal buildingblocks of Marvell ARMADA SoCs - APN806, APN807 and CP110Change-Id: I9559343788fa2e5eb47e6384a4a7d47408787c02Signed-off-by: Hanna Hawa <hannah@marvell.com>Signed-off-by: Konstantin Porotchkin <kostap@marvell.com>