Kconfig: separate memory mapped boot device from SPI
Make the indication of the boot device being memory mapped separate from SPI. However, retain the same defaults that previously existed. BUG=chrome-os-partner:56151 Change-Id: I06f138078c47a1e4b4b3edbdbf662f171e11c9d4 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/16228 Tested-by: build bot (Jenkins) Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-by: Martin Roth <martinroth@google.com>
This commit is contained in:
committed by
Martin Roth
parent
d3d77beffa
commit
16c173fdf5
@ -586,8 +586,8 @@ static int elog_shrink(void)
|
||||
*/
|
||||
static inline u8 *elog_flash_offset_to_address(void)
|
||||
{
|
||||
/* Only support memory-mapped SPI devices. */
|
||||
if (!IS_ENABLED(CONFIG_SPI_FLASH_MEMORY_MAPPED))
|
||||
/* Only support memory-mapped devices. */
|
||||
if (!IS_ENABLED(CONFIG_BOOT_DEVICE_MEMORY_MAPPED))
|
||||
return NULL;
|
||||
|
||||
if (!elog_spi)
|
||||
|
Reference in New Issue
Block a user