diff options
| author | Tom Rini <trini@ti.com> | 2014-04-03 07:52:56 -0400 |
|---|---|---|
| committer | Tom Rini <trini@ti.com> | 2014-04-17 17:24:37 -0400 |
| commit | 79b079f35c31bab26e45a526bd128891ab6c5c1d (patch) | |
| tree | a230cbff091260698d90158830b963929cd9b148 /arch/arm/cpu/armv7/omap-common/boot-common.c | |
| parent | fa1a73fa87bfd204f56224d3ef7ab1ab486ca95f (diff) | |
| download | blackbird-obmc-uboot-79b079f35c31bab26e45a526bd128891ab6c5c1d.tar.gz blackbird-obmc-uboot-79b079f35c31bab26e45a526bd128891ab6c5c1d.zip | |
dra7xx_evm: Add QSPI_4 support, qspiboot build target
We previously only supported QSPI_1 (single) support. Add QSPI_4 (quad)
read support as well. This means we can be given one of two boot device
values, but don't care which it is, so perform a fixup on the QSPI_4
value. We add a qspiboot build target to better show how you would use
QSPI as a boot device in deployment. When we boot from QSPI, we can
check the environment for 'boot_os' to control Falcon Mode.
Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
Signed-off-by: Tom Rini <trini@ti.com>
Diffstat (limited to 'arch/arm/cpu/armv7/omap-common/boot-common.c')
| -rw-r--r-- | arch/arm/cpu/armv7/omap-common/boot-common.c | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/arch/arm/cpu/armv7/omap-common/boot-common.c b/arch/arm/cpu/armv7/omap-common/boot-common.c index 52e0f4a6cf..3033564760 100644 --- a/arch/arm/cpu/armv7/omap-common/boot-common.c +++ b/arch/arm/cpu/armv7/omap-common/boot-common.c @@ -56,6 +56,17 @@ void save_omap_boot_params(void) *((u32 *)(dev_data + BOOT_MODE_OFFSET)); } } + +#ifdef CONFIG_DRA7XX + /* + * We get different values for QSPI_1 and QSPI_4 being used, but + * don't actually care about this difference. Rather than + * mangle the later code, if we're coming in as QSPI_4 just + * change to the QSPI_1 value. + */ + if (gd->arch.omap_boot_params.omap_bootdevice == 11) + gd->arch.omap_boot_params.omap_bootdevice = BOOT_DEVICE_SPI; +#endif } #ifdef CONFIG_SPL_BUILD |
