67e4df8b65
The SPI drivers for the various chipsets are not consistent in their handling of when they are accessible. Coupled with the unknown ordering of boot_device_init() being called this can lead to unexpected behavior (probing failures or hangs). Instead move the act of initializing the SPI flash boot device to when the various infrastructure requires its usage when it calls boot_device_rw(). Those platforms utilizing the RW boot device would need to ensure their SPI drivers are functional and ready when the call happens. This further removes any other systems failing to boot as reported in https://ticket.coreboot.org/issues/67. BUG=chrome-os-partner:56151 Change-Id: Ib3bddf5e26bf5322f3dd20345eeef6bee40f0f66 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/16300 Tested-by: build bot (Jenkins) Tested-by: Raptor Engineering Automated Test Stand <noreply@raptorengineeringinc.com> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-by: Martin Roth <martinroth@google.com> Reviewed-by: Werner Zeh <werner.zeh@siemens.com> |
||
|---|---|---|
| .. | ||
| tpm | ||
| adesto.c | ||
| amic.c | ||
| atmel.c | ||
| boot_device_rw_nommap.c | ||
| cbfs_spi.c | ||
| eon.c | ||
| gigadevice.c | ||
| Kconfig | ||
| macronix.c | ||
| Makefile.inc | ||
| spansion.c | ||
| spi_flash.c | ||
| spi_flash_internal.h | ||
| spiconsole.c | ||
| sst.c | ||
| stmicro.c | ||
| winbond.c | ||