summaryrefslogtreecommitdiffstats
path: root/drivers/mtd/devices/Makefile
diff options
context:
space:
mode:
authorBoris Brezillon <boris.brezillon@bootlin.com>2019-08-06 07:10:40 +0200
committerTudor Ambarus <tudor.ambarus@microchip.com>2019-08-12 09:54:12 +0200
commitb35b9a10362d203451d920d01ab8d6cd55cbaf2a (patch)
tree2fd177bda4ffe597cf2c826ccbbf54a1c7626ea6 /drivers/mtd/devices/Makefile
parentmtd: spi-nor: always use bounce buffer for register read/writes (diff)
downloadlinux-b35b9a10362d203451d920d01ab8d6cd55cbaf2a.tar.xz
linux-b35b9a10362d203451d920d01ab8d6cd55cbaf2a.zip
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/devices/Makefile')
-rw-r--r--drivers/mtd/devices/Makefile1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/mtd/devices/Makefile b/drivers/mtd/devices/Makefile
index 94895eab3066..991c8d12c016 100644
--- a/drivers/mtd/devices/Makefile
+++ b/drivers/mtd/devices/Makefile
@@ -12,7 +12,6 @@ obj-$(CONFIG_MTD_MTDRAM) += mtdram.o
obj-$(CONFIG_MTD_LART) += lart.o
obj-$(CONFIG_MTD_BLOCK2MTD) += block2mtd.o
obj-$(CONFIG_MTD_DATAFLASH) += mtd_dataflash.o
-obj-$(CONFIG_MTD_M25P80) += m25p80.o
obj-$(CONFIG_MTD_MCHP23K256) += mchp23k256.o
obj-$(CONFIG_MTD_SPEAR_SMI) += spear_smi.o
obj-$(CONFIG_MTD_SST25L) += sst25l.o