Kconfig: lay groundwork for not assuming SPI flash boot device
commit4a36c4e9fc66bf442f46e1e6d742b2d6c50a2ae1
authorAaron Durbin <adurbin@chromium.org>
Thu, 11 Aug 2016 16:02:26 +0000 (11 11:02 -0500)
committerMartin Roth <martinroth@google.com>
Thu, 18 Aug 2016 04:18:21 +0000 (18 06:18 +0200)
tree0370c6f41f8eb72c35fbfa915f0226bb312f5d13
parent2d97cb1be50acdf7e7604dd666d52cb9765de018
Kconfig: lay groundwork for not assuming SPI flash boot device

Almost all boards and chipsets within the codebase assume or
use SPI flash as the boot device. Therefore, provide an option
for the boards/chipsets which don't currently support SPI flash
as the boot device. The default is to assume SPI flash is the
boot device unless otherwise instructed. This falls in line
with the current assumptions, but it also allows one to
differentiate a platform desiring SPI flash support while it not
being the actual boot device.

One thing to note is that while google/daisy does boot with SPI
flash part no SPI API interfaces were ever implemented. Therefore,
mark that board as not having a SPI boot device.

BUG=chrome-os-partner:56151

Change-Id: Id4e0b4ec5e440e41421fbb6d0ca2be4185b62a6e
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://review.coreboot.org/16191
Tested-by: build bot (Jenkins)
Reviewed-by: Furquan Shaikh <furquan@google.com>
src/Kconfig
src/cpu/allwinner/a10/Kconfig
src/cpu/ti/am335x/Kconfig
src/drivers/spi/Kconfig
src/mainboard/emulation/qemu-armv7/Kconfig
src/mainboard/emulation/qemu-power8/Kconfig
src/mainboard/emulation/qemu-riscv/Kconfig
src/mainboard/emulation/spike-riscv/Kconfig
src/mainboard/google/daisy/Kconfig