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: Ibdd7c8754f9bf560a878136b1f55238e2c2549d3
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://review.coreboot.org/16193
Reviewed-by: Andrey Petrov <andrey.petrov@intel.com>
Tested-by: build bot (Jenkins)
Reviewed-by: Furquan Shaikh <furquan@google.com>
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>

src/drivers/elog/elog.c

@@ -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)

src/drivers/spi/Kconfig

@@ -32,13 +32,6 @@ config SPI_ATOMIC_SEQUENCING
 	  in the SPI controller. Hardware manages the transaction instead of
 	  software. This is common on x86 platforms.
 
-config SPI_FLASH_MEMORY_MAPPED
-	bool
-	default y if ARCH_X86
-	default n if !ARCH_X86
-	help
-	  Inform system if SPI is memory-mapped or not.
-
 config SPI_FLASH_SMM
 	bool "SPI flash driver support in SMM"
 	default n