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

[Prabhakar Kushwaha]

Hi Jagan,

> -----Original Message-----
> From: Jagan Teki [mailto:jagannadh.teki at gmail.com]
> Sent: Friday, May 18, 2018 11:54 AM
> To: Prabhakar Kushwaha <prabhakar.kushwaha at nxp.com>
> Cc: u-boot at lists.denx.de
> Subject: Re: mtd: spi-nor: new NXP FlexSPI driver location & framework to use ?
> 
> On Fri, May 18, 2018 at 10:31 AM, Prabhakar Kushwaha
> <prabhakar.kushwaha at nxp.com> wrote:
> > Dear Jagan,
> >
> >
> >> -----Original Message-----
> >> From: Jagan Teki [mailto:jagannadh.teki at gmail.com]
> >> Sent: Friday, May 18, 2018 10:24 AM
> >> To: Prabhakar Kushwaha <prabhakar.kushwaha at nxp.com>
> >> Cc: u-boot at lists.denx.de
> >> Subject: Re: mtd: spi-nor: new NXP FlexSPI driver location &
> >> framework to use ?
> >>
> >> On Thu, May 17, 2018 at 4:49 PM, Prabhakar Kushwaha
> >> <prabhakar.kushwaha at nxp.com> wrote:
> >> > Dear Jagan,
> >> >
> >> >> -----Original Message-----
> >> >> From: U-Boot [mailto:u-boot-bounces at lists.denx.de] On Behalf Of
> >> >> Prabhakar Kushwaha
> >> >> Sent: Monday, May 14, 2018 6:55 PM
> >> >> To: Jagan Teki <jagannadh.teki at gmail.com>
> >> >> Cc: u-boot at lists.denx.de
> >> >> Subject: Re: [U-Boot] mtd: spi-nor: new NXP FlexSPI driver
> >> >> location & framework to use ?
> >> >>
> >> >> Thanks Jagan,
> >> >>
> >> >> > -----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.
> >> >>
> >> >> This means, flexspi controller driver should be upstream'ed via
> >> >> u-boot- spi/drivers/mtd/spi-nor branch mtd-spinor-working
> >> >>
> >> >
> >> > Please help me with the query.
> >> > We don’t want to end up with 2 FlexSPI drivers being posted in upstream.
> >>
> >> Let me understand is this FlexSPI is spi-nor controller, is it Linux
> >> upstreamed or ML?
> >
> > RFC patch
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpatchw
> ork.ozlabs.org%2Fpatch%2F894918%2F&data=02%7C01%7Cprabhakar.kushwah
> a%40nxp.com%7C32aaec29f75b416004ec08d5bc87f8f1%7C686ea1d3bc2b4c6f
> a92cd99c5c301635%7C0%7C0%7C636622214533987461&sdata=%2F8i9vHtQF1
> S5Q6Bn65HVNPIMe%2FI6eSvP%2FKmKs1gxA8U%3D&reserved=0 is under
> discussion.
> > It is with assumption of driver/mtd/spi-nor
> 
> Ohh, there is chance to move this to spi-mem is it?
> 
> >
> >> I think for now you can add it mtd/spi with UCLASS_SPI_FLASH driver,
> >> Since Boris mentioned about spi-mem(I still need to see the Linux
> >> framework for more details) which may be re-placer for spi-nor but
> >> once we decided to go with spi-mem or spi-nor then the flexspi can convert
> accordingly.
> >>
> >
> > This means,  FlexSPI should be part of driver/mtd/spi-nor for now.
> > When You decide way forward(mtd/spi or spi-mem), flexSPI driver can move
> accordingly.
> 
> Due to spi-mem, I'm holding spi-nor driver as of now. we need some discussion
> to understand how we implement it in U-Boot and decide to move further. So I
> suggest you to use existing sf where we can write UCLASS_SPI_FLASH driver.
> Hope you understand.
> 

For now, sent FlexSPI driver as per current framework i.e. driver/mtd/spi.

Wait for the new framework(either spi-mem or driver/mtd) from you. 
Once framework available migrate to that one.

Is my understanding correct?

--pk