[U-Boot] mtd: spi-nor: new NXP FlexSPI driver location & framework to use ?

[Ashish Kumar]

> -----Original Message-----
> From: Jagan Teki [mailto:jagannadh.teki at gmail.com]
> Sent: Friday, May 11, 2018 11:31 AM
> To: Prabhakar Kushwaha <prabhakar.kushwaha at nxp.com>
> Cc: Jagan Teki <jagan at amarulasolutions.com>; York Sun <york.sun at nxp.com>;
> Yogesh Narayan Gaur <yogeshnarayan.gaur at nxp.com>; Poonam Aggrwal
> <poonam.aggrwal at nxp.com>; Ashish Kumar <ashish.kumar at nxp.com>; u-
> boot at 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.kushwaha at 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 http://git.denx.de/?p=u-boot-spi.git;a=commitdiff;h=c4e68d3aa8178f6aa63a79c4f8f459c0e3ed58e8

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 ?

Regards
Ashish 
> [1]
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit.denx
> .de%2F%3Fp%3Du-boot-
> spi.git%3Ba%3Dcommitdiff%3Bh%3Dc4e68d3aa8178f6aa63a79c4f8f459c0e3ed
> 58e8&data=02%7C01%7Cashish.kumar%40nxp.com%7C2acd718de97d435bb5e
> c08d5b70489cd%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C63661
> 6152533412247&sdata=ury1R6ZYqoJbx5nuYTehZyMTo%2BFW3QPpLD1EIPUrcz
> g%3D&reserved=0
> 
> Jagan.
> 
> --
> Jagan Teki
> Free Software Engineer |
> https://emea01.safelinks.protection.outlook.com/?url=www.openedev.com&d
> ata=02%7C01%7Cashish.kumar%40nxp.com%7C2acd718de97d435bb5ec08d5b7
> 0489cd%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636616152533
> 412247&sdata=gsoI52kSNfVEE6K%2F03CWs6%2FG2Xr1L9TEhDLGmqrRWRQ%3
> D&reserved=0
> U-Boot, Linux | Upstream Maintainer
> Hyderabad, India.