Thanks Jagan, > -----Original Message----- > From: Jagan Teki [mailto:[email protected]] > Sent: Friday, May 11, 2018 11:31 AM > To: Prabhakar Kushwaha <[email protected]> > Cc: Jagan Teki <[email protected]>; York Sun > <[email protected]>; Yogesh Narayan Gaur > <[email protected]>; Poonam Aggrwal > <[email protected]>; Ashish Kumar <[email protected]>; u- > [email protected] > Subject: Re: mtd: spi-nor: new NXP FlexSPI driver location & framework to > use ? > > On Fri, May 11, 2018 at 11:08 AM, Prabhakar Kushwaha > <[email protected]> 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 --pk _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
