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>
This commit is contained in:
committed by
Martin Roth
parent
2d97cb1be5
commit
4a36c4e9fc
@@ -14,5 +14,6 @@ config CPU_SPECIFIC_OPTIONS
|
||||
select HAVE_UART_SPECIAL
|
||||
select BOOTBLOCK_CONSOLE
|
||||
select UART_OVERRIDE_REFCLK
|
||||
select BOOT_DEVICE_NOT_SPI_FLASH
|
||||
|
||||
endif # if CPU_ALLWINNER_A10
|
||||
|
@@ -8,5 +8,6 @@ config CPU_TI_AM335X
|
||||
select BOOTBLOCK_CONSOLE
|
||||
select GENERIC_UDELAY
|
||||
select UART_OVERRIDE_REFCLK
|
||||
select BOOT_DEVICE_NOT_SPI_FLASH
|
||||
bool
|
||||
default n
|
||||
|
Reference in New Issue
Block a user