On Thu, Dec 13, 2018 at 2:10 AM Boris Brezillon <boris.brezil...@bootlin.com> wrote: > > Hi Jagan, > > On Thu, 13 Dec 2018 01:55:08 +0530 > Jagan Teki <ja...@amarulasolutions.com> wrote: > > > On Wed, Dec 12, 2018 at 11:08 PM Vignesh R <vigne...@ti.com> wrote: > > > > > > Add non DM version of SPI_MEM to support easy migration to new SPI NOR > > > framework. This can be removed once DM_SPI conversion is complete. > > > > Our intention to use new driver to follow dm, why we need to support > > non-dm? any usecases? > > Looks like we're having the same discussion over and over. Vignesh is > dropping spi_flash.c which AFAICT was not depending on DM_SPI, so, if > we want to keep everyone happy while getting rid of some legacy code, > that's the only solution. DM conversion is a nice goal, but it's kind > of orthogonal to what Vignesh is working on. If DM_SPI conversion > happens before the spi-nor stuff is merged (which I doubt) then this > patch can simply be dropped.
spi_flash.c is a core code not a specific driver it belongs. spi-mem is new feature driver how come new driver will support legacy non-dm do we have legacy use for that(ie what I'm asking about usecase) _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
