Hello Jagan, > -----Original Message----- > From: Jagan Teki [mailto:jagannadh.t...@gmail.com] > Sent: Monday, May 14, 2018 3:18 PM > To: Ashish Kumar <ashish.ku...@nxp.com> > Cc: Jagan Teki <ja...@amarulasolutions.com>; York Sun > <york....@nxp.com>; Prabhakar Kushwaha > <prabhakar.kushw...@nxp.com>; Yogesh Narayan Gaur > <yogeshnarayan.g...@nxp.com>; Poonam Aggrwal > <poonam.aggr...@nxp.com>; u-boot@lists.denx.de > Subject: Re: mtd: spi-nor: new NXP FlexSPI driver location & framework to > use ? > > On Mon, May 14, 2018 at 2:42 PM, Ashish Kumar <ashish.ku...@nxp.com> > wrote: > > > > > >> -----Original Message----- > >> From: Jagan Teki [mailto:jagannadh.t...@gmail.com] > >> Sent: Friday, May 11, 2018 11:31 AM > >> To: Prabhakar Kushwaha <prabhakar.kushw...@nxp.com> > >> Cc: Jagan Teki <ja...@amarulasolutions.com>; York Sun > >> <york....@nxp.com>; Yogesh Narayan Gaur > <yogeshnarayan.g...@nxp.com>; > >> Poonam Aggrwal <poonam.aggr...@nxp.com>; Ashish Kumar > >> <ashish.ku...@nxp.com>; u- b...@lists.denx.de > >> Subject: Re: mtd: spi-nor: new NXP FlexSPI driver location & framework to > use ? > >> > >> On Fri, May 11, 2018 at 11:08 AM, Prabhakar Kushwaha > >> <prabhakar.kushw...@nxp.com> wrote: > >> > Dear Jagan, > >> > > >> > NXP is coming up with new FlexSPI controller. It is similar to > >> > existing QSPI with > >> enhanced feature-set. > >> > We have the driver ready as per existing framework i.e. driver/spi. > >> > > >> > From recend discussion, we go to know about framework change. > >> > Migration of qspi drivers in u-boot-spi/drivers/mtd/spi-nor/ > >> git://git.denx.de/u-boot-spi.git branch mtd-spinor-working. > >> > > >> > We are in dilemma for sending FlexSPI driver upstream. > >> > Do we follow existing framework i.e. driver/spi or new proposed > framework > >> i.e. u-boot-spi/drivers/mtd/spi-nor/ > >> > > >> > Also, do we have any timeline of u-boot-spi/drivers/mtd/spi-nor/ to > >> > become > >> default. > >> > >> Idea is to move spi-nor, mtd-spinor-working is paused because of > >> non-dm drivers accessing. We are clear that we can't create another > >> legacy layer to access spi-nor for the sake of non-dm driver to work > >> which eventually ended-up another mess and also no one take care of > >> non-dm conversion to dm if we give such feasibility. So we exported a > >> deadline for full SPI/SPI_FLASH DM conversion till v2018.09. Once all these > relevant conversion done, will try to move. > >> > > Hello Jagan, > > > > You have mentioned here > > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit. > > denx.de%2F%3Fp%3Du-boot- > spi.git%3Ba%3Dcommitdiff%3Bh%3Dc4e68d3aa8178f6 > > > aa63a79c4f8f459c0e3ed58e8&data=02%7C01%7Cashish.kumar%40nxp.com% > 7Ca4d3 > > > 2392ca7d4a0a5ead08d5b97fbeb3%7C686ea1d3bc2b4c6fa92cd99c5c301635% > 7C0%7C > > > 0%7C636618880665899108&sdata=yAOW42d%2F%2B6W47PCURhbnzyD3sfS > VloRtafRz% > > 2FBJmrRM%3D&reserved=0 > > > > Snip from above link: > > +Partially converted: > > + drivers/spi/atcspi200_spi.c > > + drivers/spi/davinci_spi.c > > + drivers/spi/fsl_dspi.c > > + drivers/spi/fsl_qspi.c > > > > That fsl_qspi.c is partial converted to DM model, is there any guide line to > follow for missing stuff ? > > We should fully convert the driver into dm, no #ifdef CONFIG_DM_SPI
Could you please let me know if timeline for migration to full-DM mode has moved forward ? My patch(drivers/spi/fsl_qspi.c) is dependent upon below mentioned patch-sets acceptance. http://patchwork.ozlabs.org/patch/935860/ http://patchwork.ozlabs.org/patch/935858/ Regards Ashish _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
