Searched hist:"9 c740a58e140dfab13be1e5f41b427737428c210" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_ARM-atf/plat/socionext/uniphier/ |
| H A D | uniphier_xlat_setup.c | 9c740a58e140dfab13be1e5f41b427737428c210 Tue Jan 30 10:30:39 UTC 2018 Masahiro Yamada <yamada.masahiro@socionext.com> uniphier: allocate xlat region of on-chip SRAM only when needed
Currently, the xlat region of the on-chip SRAM is always allocated
for all BL images.
The access to the on-chip SRAM is necessary for loading images from
a USB memory device (i.e. when updating firmware), so unneeded for
the usual boot procedure.
To avoid this waste, allocate the xlat region dynamically only for
BL2, and only when it is necessary.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
|
| H A D | uniphier_io_storage.c | 9c740a58e140dfab13be1e5f41b427737428c210 Tue Jan 30 10:30:39 UTC 2018 Masahiro Yamada <yamada.masahiro@socionext.com> uniphier: allocate xlat region of on-chip SRAM only when needed
Currently, the xlat region of the on-chip SRAM is always allocated
for all BL images.
The access to the on-chip SRAM is necessary for loading images from
a USB memory device (i.e. when updating firmware), so unneeded for
the usual boot procedure.
To avoid this waste, allocate the xlat region dynamically only for
BL2, and only when it is necessary.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
|