Searched hist:"81646055138 ed431ca155382ccf7c286f4d52e7f" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_ARM-atf/include/drivers/marvell/mochi/ |
| H A D | cp110_setup.h | 81646055138ed431ca155382ccf7c286f4d52e7f Fri Aug 18 14:42:12 UTC 2017 Grzegorz Jaszczyk <jaz@semihalf.com> plat: marvell: armada: add support for loading MG CM3 images
In order to access MG SRAM, the amb bridge needs to be configured which is
done in bl2 platform init.
For MG CM3, the image is only loaded to its SRAM and the CM3 itself is
left 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. This
can happen e.g. when appropriate device-tree setup (which has enabled
802.3 auto-neg) will be chosen. In other cases the MG CM3 should not be
running.
Change-Id: I816ea14e3a7174eace068ec44e3cc09998d0337e
Signed-off-by: Grzegorz Jaszczyk <jaz@semihalf.com>
|
| /rk3399_ARM-atf/drivers/marvell/mochi/ |
| H A D | cp110_setup.c | 81646055138ed431ca155382ccf7c286f4d52e7f Fri Aug 18 14:42:12 UTC 2017 Grzegorz Jaszczyk <jaz@semihalf.com> plat: marvell: armada: add support for loading MG CM3 images
In order to access MG SRAM, the amb bridge needs to be configured which is
done in bl2 platform init.
For MG CM3, the image is only loaded to its SRAM and the CM3 itself is
left 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. This
can happen e.g. when appropriate device-tree setup (which has enabled
802.3 auto-neg) will be chosen. In other cases the MG CM3 should not be
running.
Change-Id: I816ea14e3a7174eace068ec44e3cc09998d0337e
Signed-off-by: Grzegorz Jaszczyk <jaz@semihalf.com>
|