Dear Jagan,
-----Original Message----- From: U-Boot [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Prabhakar Kushwaha Sent: Monday, May 14, 2018 6:55 PM To: Jagan Teki jagannadh.teki@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.teki@gmail.com] Sent: Friday, May 11, 2018 11:31 AM To: Prabhakar Kushwaha prabhakar.kushwaha@nxp.com Cc: Jagan Teki jagan@amarulasolutions.com; York Sun york.sun@nxp.com; Yogesh Narayan Gaur
Poonam Aggrwal poonam.aggrwal@nxp.com; Ashish Kumar ashish.kumar@nxp.com; u- boot@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@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.
--pk