Searched hist:d2f18c275eef1eaca58919fb34ea0abf3bfbddcd (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/arch/arm/include/asm/arch-omap4/ |
| H A D | sys_proto.h | d2f18c275eef1eaca58919fb34ea0abf3bfbddcd Thu Jul 21 13:09:59 UTC 2011 Aneesh V <aneesh@ti.com> omap4: utility function to identify the context of hw init
The basic hardware init of OMAP4(s_init()) can happen in 4
different contexts:
1. SPL running from SRAM
2. U-Boot running from FLASH
3. Non-XIP U-Boot loaded to SDRAM by SPL
4. Non-XIP U-Boot loaded to SDRAM by ROM code using the
Configuration Header feature
What level of hw initialization gets done depends on this
context. Add a utility function to find this context.
Signed-off-by: Aneesh V <aneesh@ti.com>
Signed-off-by: Sandeep Paulraj <s-paulraj@ti.com>
|
| /rk3399_rockchip-uboot/arch/arm/include/asm/ |
| H A D | omap_common.h | d2f18c275eef1eaca58919fb34ea0abf3bfbddcd Thu Jul 21 13:09:59 UTC 2011 Aneesh V <aneesh@ti.com> omap4: utility function to identify the context of hw init
The basic hardware init of OMAP4(s_init()) can happen in 4
different contexts:
1. SPL running from SRAM
2. U-Boot running from FLASH
3. Non-XIP U-Boot loaded to SDRAM by SPL
4. Non-XIP U-Boot loaded to SDRAM by ROM code using the
Configuration Header feature
What level of hw initialization gets done depends on this
context. Add a utility function to find this context.
Signed-off-by: Aneesh V <aneesh@ti.com>
Signed-off-by: Sandeep Paulraj <s-paulraj@ti.com>
|