summaryrefslogtreecommitdiff
path: root/drivers/mtd
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2015-03-06 13:19:06 -0700
committerSimon Glass <sjg@chromium.org>2015-04-18 11:11:38 -0600
commit949dd81b43f8f8499320dbb20266abdd4e9ae303 (patch)
treee2aada135dea9289c478c8e57be15a1c8ab03a90 /drivers/mtd
parent892cac72e44d54add772f81fee01ab64b006b88b (diff)
downloadu-boot-imx-949dd81b43f8f8499320dbb20266abdd4e9ae303.zip
u-boot-imx-949dd81b43f8f8499320dbb20266abdd4e9ae303.tar.gz
u-boot-imx-949dd81b43f8f8499320dbb20266abdd4e9ae303.tar.bz2
sandbox: Move CONFIG_SPI_FLASH_SANDBOX to Kconfig
Move this over to Kconfig and tidy up. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/mtd')
-rw-r--r--drivers/mtd/spi/Kconfig10
1 files changed, 10 insertions, 0 deletions
diff --git a/drivers/mtd/spi/Kconfig b/drivers/mtd/spi/Kconfig
index fd2d7ac..ac6d09f 100644
--- a/drivers/mtd/spi/Kconfig
+++ b/drivers/mtd/spi/Kconfig
@@ -12,3 +12,13 @@ config DM_SPI_FLASH
during the transition parent. SPI and SPI flash must be
enabled together (it is not possible to use driver model
for one and not the other).
+
+config SPI_FLASH_SANDBOX
+ bool "Support sandbox SPI flash device"
+ depends on SANDBOX && DM_SPI_FLASH
+ help
+ Since sandbox cannot access real devices, an emulation mechanism is
+ provided instead. Drivers can be connected up to the sandbox SPI
+ bus (see CONFIG_SANDBOX_SPI) and SPI traffic will be routed to this
+ device. Typically the contents of the emulated SPI flash device is
+ stored in a file on the host filesystem.