public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] sf: New SF-NOR framework
Date: Tue, 11 Nov 2014 23:56:00 +0100	[thread overview]
Message-ID: <201411112356.00436.marex@denx.de> (raw)
In-Reply-To: <CAD6G_RRg163x3PJo3=A_eu4xFtf=aTOXpV9sB+9FO5_r1GPmfg@mail.gmail.com>

On Tuesday, November 11, 2014 at 10:37:33 PM, Jagan Teki wrote:
> On 12 November 2014 02:52, Marek Vasut <marex@denx.de> wrote:
> > On Tuesday, November 11, 2014 at 09:50:35 PM, Jagannadha Sutradharudu
> > Teki
> > 
> > wrote:
> >> This is long lasting work that I did last few months back,
> >> I'm sure it's where much need now.
> >> 
> >> - spi driver: drivers/spi/fsl_qspi.c
> >> - flash attributes in spi_slave {} and
> >> - etc ...
> >> making spi subsystem becomes more flash specific rather operating
> >> as a generic spi bus. So SF-NOR divides normal spi flash operations
> >> through generic SPI API's(sf_spi.c) and more spi flash(sf) specific
> >> operations through SF NOR API's.
> >> 
> >> So the controllers those are operating more on flash needs to
> >> write a driver on drivers/mtd/spi/ example fsl_qspi.c
> >> 
> >> I have not tested more accuratly as of now, will come back again
> >> with new feature additions/removal, zynq_qspi additions and more...
> >> 
> >> Note: dm-spi ops can gets effected with this new framework
> >> { .ops            = &spi_flash_std_ops, } and will fix that in next
> >> version patches.
> >> 
> >> Signed-off-by: Jagannadha Sutradharudu Teki <jagannadh.teki@gmail.com>
> > 
> > I have but a general question -- why did you not just import the spi-nor
> > framework from Linux ?
> 
> Well, importing spi-nor from Linux is may not be a good idea as we
> have a working stuff
> at our end along with different dependencies and I'm sure this will
> becomes similar way as
> spi-nor at some point of time.

What you said doesn't add up to me -- you introduced a completely new framework 
in this patch, right ? So what exact "working stuff" do we have if this is a 
completely new code ?

Compared to that, the SPI NOR framework in Linux is being actively maintained 
and actively used for a while now, so it's actually a proven code already. Also, 
we just recently resynced MTD subsystem with Linux, adding the SPI NOR framework 
which is based on that same MTD framework would probably be pretty 
straighforward.

Best regards,
Marek Vasut

  reply	other threads:[~2014-11-11 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 20:50 [U-Boot] [RFC PATCH] sf: New SF-NOR framework Jagannadha Sutradharudu Teki
2014-11-11 21:22 ` Marek Vasut
2014-11-11 21:37   ` Jagan Teki
2014-11-11 22:56     ` Marek Vasut [this message]
2014-11-12  0:19       ` Jagan Teki
2014-11-12 22:16         ` Marek Vasut
2014-11-16 18:58           ` Jagan Teki

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=201411112356.00436.marex@denx.de \
    --to=marex@denx.de \
    --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