summaryrefslogtreecommitdiff
path: root/drivers/mtd/spi-nor/Kconfig
diff options
context:
space:
mode:
authorBoris Brezillon <boris.brezillon@bootlin.com>2019-08-06 08:10:40 +0300
committerTudor Ambarus <tudor.ambarus@microchip.com>2019-08-12 10:54:12 +0300
commitb35b9a10362d203451d920d01ab8d6cd55cbaf2a (patch)
tree2fd177bda4ffe597cf2c826ccbbf54a1c7626ea6 /drivers/mtd/spi-nor/Kconfig
parentf173f26a4d543fa57e6ed9505bbbbf9bec61f544 (diff)
downloadlinux-b35b9a10362d203451d920d01ab8d6cd55cbaf2a.tar.xz
mtd: spi-nor: Move m25p80 code in spi-nor.c
The m25p80 driver is actually a generic wrapper around the spi-mem layer. Not only the driver name is misleading, but we'd expect such a common logic to be directly available in the core. Another reason for moving this code is that SPI NOR controller drivers should progressively be replaced by SPI controller drivers implementing the spi_mem_ops interface, and when the conversion is done, we should have a single spi-nor driver directly interfacing with the spi-mem layer. While moving the code we also fix a longstanding issue when non-DMA-able buffers are passed by the MTD layer. Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Diffstat (limited to 'drivers/mtd/spi-nor/Kconfig')
-rw-r--r--drivers/mtd/spi-nor/Kconfig2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/mtd/spi-nor/Kconfig b/drivers/mtd/spi-nor/Kconfig
index 6de83277ce8b..f237fcdf7f86 100644
--- a/drivers/mtd/spi-nor/Kconfig
+++ b/drivers/mtd/spi-nor/Kconfig
@@ -2,6 +2,8 @@
menuconfig MTD_SPI_NOR
tristate "SPI-NOR device support"
depends on MTD
+ depends on MTD && SPI_MASTER
+ select SPI_MEM
help
This is the framework for the SPI NOR which can be used by the SPI
device drivers and the SPI-NOR device driver.