summaryrefslogtreecommitdiff
path: root/drivers/power/exynos-tmu.c
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2013-07-10 23:08:10 -0700
committerTom Rini <trini@ti.com>2013-07-12 10:32:39 -0400
commitf320a4d845ab160dd539888280b6452deebdb3d0 (patch)
tree82ab3ab1b74dcfa79dcd7de4acf0d3f7c27a3e0f /drivers/power/exynos-tmu.c
parent7af26b1669b75a02e1cfaa68ac526897e790af84 (diff)
downloadu-boot-imx-f320a4d845ab160dd539888280b6452deebdb3d0.zip
u-boot-imx-f320a4d845ab160dd539888280b6452deebdb3d0.tar.gz
u-boot-imx-f320a4d845ab160dd539888280b6452deebdb3d0.tar.bz2
bootm: Use selected configuration for ramdisk and fdt
If a specific configuraion is selected by the bootm command, e.g. with 'bootm 84000000#recoveryconf' we must honour this for not just the kernel, but also the ramdisk and FDT. In the conversion to using a common fit_image_load() function for loading images from FITs (commits a51ec63 and 53f375f) this feature was lost. Reinstate it by passing the selected configuration back from fit_image_load() to boot_get_kernel(), then use this configuration (which is stored in images->fit_uname_cfg) in both boot_get_ramdisk() and boot_get_fdt(). Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/power/exynos-tmu.c')
0 files changed, 0 insertions, 0 deletions