On Fri, May 18, 2018 at 10:31 AM, Prabhakar Kushwaha <prabhakar.kushw...@nxp.com> wrote: > Dear Jagan, > > >> -----Original Message----- >> From: Jagan Teki [mailto:jagannadh.t...@gmail.com] >> Sent: Friday, May 18, 2018 10:24 AM >> To: Prabhakar Kushwaha <prabhakar.kushw...@nxp.com> >> Cc: u-boot@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.kushw...@nxp.com> wrote: >> > Dear Jagan, >> > >> >> -----Original Message----- >> >> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of >> >> Prabhakar Kushwaha >> >> Sent: Monday, May 14, 2018 6:55 PM >> >> To: Jagan Teki <jagannadh.t...@gmail.com> >> >> Cc: u-boot@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.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. >> >> >> >> 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 http://patchwork.ozlabs.org/patch/894918/ 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. Jagan. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot