summaryrefslogtreecommitdiff
path: root/board/boundary/nitrogen6x/1066mhz_4x256mx16.cfg
diff options
context:
space:
mode:
authorLokesh Vutla <lokeshvutla@ti.com>2016-10-14 10:35:23 +0530
committerTom Rini <trini@konsulko.com>2016-11-21 09:49:58 -0500
commitc704a99dff693d3e2d0fe1ad095febb89f872de9 (patch)
tree009a2ed64e406d38af89406f40d07575815f3d6f /board/boundary/nitrogen6x/1066mhz_4x256mx16.cfg
parent693d4c9f1dc40fcf24ced459bc4d1b46db33298a (diff)
downloadu-boot-imx-c704a99dff693d3e2d0fe1ad095febb89f872de9.zip
u-boot-imx-c704a99dff693d3e2d0fe1ad095febb89f872de9.tar.gz
u-boot-imx-c704a99dff693d3e2d0fe1ad095febb89f872de9.tar.bz2
ARM: AMx3xx: Allow arch specific code to use early DM
Early system initialization is being done before initf_dm is being called in U-Boot. Then system will fail to boot if any of the DM enabled driver is being called in this system initialization code. So, rearrange the code a bit so that DM enabled drivers can be called during early system initialization. This is inspired by commit e850ed82bce8 ("ARM: OMAP4+: Allow arch specific code to use early DM") Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'board/boundary/nitrogen6x/1066mhz_4x256mx16.cfg')
0 files changed, 0 insertions, 0 deletions