To follow spi-nor notation replaced CONFIG_SPI_FLASH_SANDBOX
with CONFIG_SPI_NOR_SANDBOX.

Cc: Simon Glass <s...@chromium.org>
Cc: Bin Meng <bmeng...@gmail.com>
Signed-off-by: Jagan Teki <jt...@openedev.com>
---
 drivers/mtd/spi-nor/Kconfig  | 10 ++++++++++
 drivers/mtd/spi-nor/Makefile |  1 +
 2 files changed, 11 insertions(+)

diff --git a/drivers/mtd/spi-nor/Kconfig b/drivers/mtd/spi-nor/Kconfig
index 12dcede..cdef6aa 100644
--- a/drivers/mtd/spi-nor/Kconfig
+++ b/drivers/mtd/spi-nor/Kconfig
@@ -98,6 +98,16 @@ config SPI_FLASH_WINBOND
        help
          Add support for various Winbond SPI flash chips (W25xxx)
 
+config SPI_NOR_SANDBOX
+       bool "Support sandbox SPI flash device"
+       depends on SANDBOX
+       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.
+
 endif # MTD_SPI_NOR
 
 config MTD_DATAFLASH
diff --git a/drivers/mtd/spi-nor/Makefile b/drivers/mtd/spi-nor/Makefile
index 525fccd..a4bd5ba 100644
--- a/drivers/mtd/spi-nor/Makefile
+++ b/drivers/mtd/spi-nor/Makefile
@@ -17,3 +17,4 @@ endif
 
 obj-$(CONFIG_MTD_M25P80)       += m25p80.o
 obj-$(CONFIG_MTD_DATAFLASH)    += mtd_dataflash.o
+obj-$(CONFIG_SPI_NOR_SANDBOX)  += sandbox.o
-- 
1.9.1

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to