public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mtd: spi-nor: new NXP FlexSPI driver location & framework to use ?
Date: Sat, 12 May 2018 07:50:23 +0200	[thread overview]
Message-ID: <20180512075023.01ccf981@bbrezillon> (raw)
In-Reply-To: <CAD6G_RRretNQ09cWzAu1-rYrWgzyHD6_OemZ3v8-JFZExE=P0g@mail.gmail.com>

Hi Jagan,

On Fri, 11 May 2018 11:30:43 +0530
Jagan Teki <jagannadh.teki@gmail.com> wrote:

> 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. 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.

Just for the record, the spi-mem interface has been accepted in Linux
[1] (should be there in 4.18). From now on, I'll try to encourage people
move existing spi-nor controller drivers to the SPI subsystem, and I'll
definitely ask new QPSI drivers to use this interface (and extend it if
needed).

So, I'm not sure creating this spi-nor subsystem in uboot is a good
idea anymore. Of course, it's up to you to decide, but if you take this
path you'll run into the same problem we had in Linux:

 - how to support SPI NANDs in a clean and efficient way
 - how to support both memory-like operations and regular SPI transfers
   with the same driver

Regards,

Boris

[1]https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git/commit/?h=for-4.18&id=c36ff266dc82f4ae797a6f3513c6ffa344f7f1c7

  parent reply	other threads:[~2018-05-12  5:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11  5:38 [U-Boot] mtd: spi-nor: new NXP FlexSPI driver location & framework to use ? Prabhakar Kushwaha
2018-05-11  6:00 ` Jagan Teki
2018-05-11 11:37   ` Prabhakar Kushwaha
2018-05-12  5:50   ` Boris Brezillon [this message]
2018-05-14  9:12   ` Ashish Kumar
2018-05-14  9:47     ` Jagan Teki
2018-05-14 13:24   ` Prabhakar Kushwaha
2018-05-17 11:19     ` Prabhakar Kushwaha
2018-05-18  4:54       ` Jagan Teki
2018-05-18  5:01         ` Prabhakar Kushwaha
2018-05-18  6:24           ` Jagan Teki
2018-05-18 10:16             ` Prabhakar Kushwaha
2018-05-21 15:05               ` Jagan Teki
2018-05-24  3:11                 ` Prabhakar Kushwaha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180512075023.01ccf981@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox