summaryrefslogtreecommitdiffstats
path: root/arch/arm/cpu/armv7/omap4
diff options
context:
space:
mode:
authorAneesh V <aneesh@ti.com>2011-07-21 09:09:59 -0400
committerU-Boot <uboot@aari01-12.(none)>2011-08-03 12:49:19 +0200
commitd2f18c275eef1eaca58919fb34ea0abf3bfbddcd (patch)
treefabf0165cbcdee72523cb7557236237ddbad5b64 /arch/arm/cpu/armv7/omap4
parent732590b397ac608369767b2579fdca0937f8adcd (diff)
downloadtalos-obmc-uboot-d2f18c275eef1eaca58919fb34ea0abf3bfbddcd.tar.gz
talos-obmc-uboot-d2f18c275eef1eaca58919fb34ea0abf3bfbddcd.zip
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>
Diffstat (limited to 'arch/arm/cpu/armv7/omap4')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud