linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: spi-nor: Decouple SPI NOR's device_node from controller device
Date: Thu, 3 Sep 2015 18:21:46 +0200	[thread overview]
Message-ID: <201509031821.46602.marex@denx.de> (raw)
In-Reply-To: <20150902003814.GO81844@google.com>

On Wednesday, September 02, 2015 at 02:38:14 AM, Brian Norris wrote:
> On Fri, Aug 21, 2015 at 11:09:20AM +0200, Marek Vasut wrote:
> > The problem this patch is trying to address is such, that SPI NOR flash
> > devices attached to a dedicated SPI NOR controller cannot read their
> > properties from the associated struct device_node.
> > 
> > A couple of facts first:
> > 1) Each SPI NOR flash has a struct spi_nor associated with it.
> > 2) Each SPI NOR flash has certain device properties associated
> > 
> >    with it, for example the OF property 'm25p,fast-read' is a
> >    good pick. These properties are used by the SPI NOR core to
> >    select which opcodes are sent to such SPI NOR flash. These
> >    properties are coming from spi_nor .dev->device_node .
> > 
> > The problem is, that for SPI NOR controllers, the struct spi_nor .dev
> > element points to the struct device of the SPI NOR controller, not the
> > SPI NOR flash. Therefore, the associated dev->device_node also is the
> > one of the controller and therefore the SPI NOR core code is trying to
> > parse the SPI NOR controller's properties, not the properties of the
> > SPI NOR flash.
> > 
> > Note: The m25p80 driver is not affected, because the controller and
> > 
> >       the flash are the same device, so the associated device_node
> >       of the controller and the flash are the same.
> > 
> > This patch adjusts the SPI NOR core such that the device_node is not
> > picked from spi_nor .dev directly, but from a new separate spi_nor .dn
> > element.
> 
> Does it really?

Yes, it does, but I missed a bit from this patch, sorry.

> [...]
> 
> > ---
> > 
> >  drivers/mtd/devices/m25p80.c      | 1 +
> >  drivers/mtd/spi-nor/fsl-quadspi.c | 1 +
> >  drivers/mtd/spi-nor/nxp-spifi.c   | 1 +
> >  include/linux/mtd/spi-nor.h       | 3 +++
> >  4 files changed, 6 insertions(+)
> 
> ^^ I would expect to see spi-nor.c changes in the diffstat. Did you miss
> something?

Yes, sorry.

> [...]
> 
> > diff --git a/include/linux/mtd/spi-nor.h b/include/linux/mtd/spi-nor.h
> > index 1bf6f11..333999d 100644
> > --- a/include/linux/mtd/spi-nor.h
> > +++ b/include/linux/mtd/spi-nor.h
> > @@ -169,6 +169,7 @@ enum spi_nor_option_flags {
> > 
> >   * @lock:		[FLASH-SPECIFIC] lock a region of the SPI NOR
> >   * @unlock:		[FLASH-SPECIFIC] unlock a region of the SPI NOR
> >   * @priv:		the private data
> > 
> > + * @dn:			[BOARD-SPECIFIC] device node describing this 
instance
> 
> I might like to see this up near the @dev entry, for organization
> purposes.

Right, will do in V2.

      reply	other threads:[~2015-09-03 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  9:09 [PATCH] mtd: spi-nor: Decouple SPI NOR's device_node from controller device Marek Vasut
2015-08-21 14:15 ` Jonas Gorski
2015-08-21 18:34   ` Marek Vasut
2015-08-21 20:49     ` Jonas Gorski
2015-08-21 21:16       ` Marek Vasut
2015-09-02  0:30         ` Brian Norris
2015-09-03 16:20           ` Marek Vasut
2015-09-02  0:38 ` Brian Norris
2015-09-03 16:21   ` Marek Vasut [this message]

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=201509031821.46602.marex@denx.de \
    --to=marex@denx.de \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).