On Mon, 12 Feb 2018 17:20:46 +0530 Vignesh R <vigneshr@xxxxxx> wrote: > Hi, > > On Tuesday 06 February 2018 04:51 AM, Boris Brezillon wrote: > > From: Boris Brezillon <boris.brezillon@xxxxxxxxxxxxxxxxxx> > > > > Some controllers are exposing high-level interfaces to access various > > kind of SPI memories. Unfortunately they do not fit in the current > > spi_controller model and usually have drivers placed in > > drivers/mtd/spi-nor which are only supporting SPI NORs and not SPI > > memories in general. > > > > This is an attempt at defining a SPI memory interface which works for > > all kinds of SPI memories (NORs, NANDs, SRAMs). > > Wouldn't it be better if spi_mem* implementations were in separate file? > drivers/spi/spi.c is 3.5K+ lines and is bit difficult to follow. No strong opinion about where the spi_mem code should lie, so if Mark agrees I can move it to a different file and possibly make it optional with a Kconfig option. -- Boris Brezillon, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering http://bootlin.com -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html