public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Graham Moore <grmoore@opensource.altera.com>
Cc: linux-mtd@lists.infradead.org,
	Alan Tull <atull@opensource.altera.com>,
	Yves Vandervennet <yvanderv@opensource.altera.com>,
	linux-kernel@vger.kernel.org,
	Dinh Nguyen <dinguyen@opensource.altera.com>,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH V4 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver.
Date: Fri, 24 Jul 2015 21:57:05 +0200	[thread overview]
Message-ID: <201507242157.05840.marex@denx.de> (raw)
In-Reply-To: <55B27300.80801@opensource.altera.com>

On Friday, July 24, 2015 at 07:16:48 PM, Graham Moore wrote:
> On 07/24/2015 11:25 AM, Marek Vasut wrote:
> > On Friday, July 24, 2015 at 06:12:01 PM, Graham Moore wrote:
> >> On 07/24/2015 07:45 AM, Marek Vasut wrote:
> >>> On Monday, March 23, 2015 at 02:36:21 PM, Graham Moore wrote:
> >>>> Signed-off-by: Graham Moore <grmoore@opensource.altera.com>
> >>>> ---
> >>>> V2: Add cdns prefix to driver-specific bindings.
> >>>> V3: Use existing property "is-decoded-cs" instead of creating a
> >>>> duplicate, "ext-decoder".  Timing parameters are in nanoseconds, not
> >>>> master reference clocks.  Remove bus-num completely.
> >>> 
> >>> Hi!
> >>> 
> >>> do you plan to continue on this driver any soon? If not, I'd like to
> >>> take over the mainlining if you're not opposed. I'd like to see this
> >>> in mainline soon.
> >> 
> >> I don't have a problem with you taking over the mainlining.  I've been
> >> stalled on the micron quad protocol issue that Cyrille Pitchen has
> >> solved.
> > 
> > Do you mean the protocol change notification please?
> 
> Yes, that's what I mean, the protocol change notification.

OK

> >>> btw you'll need some kind of a variation on the attached two patches in
> >>> the next iteration.
> >> 
> >> I have a V5 with fixes for sparse and smatch issues.  Do you want me to
> >> post it and you add those two patches?  Alternatively I can incorporate
> >> them into my V5.
> > 
> > Please post those patches, yup, that'd be nice :)
> > 
> > Also, just squash those two micropatches into yours, no problem.
> > 
> > Be careful about the 0002 patch, see the commit message. I do NOT think
> > it is correct to pass the pdev->dev which represents the controller, not
> > the subnode, into spi_nor_scan() in cqspi_probe() . I might be wrong here
> > though, I am not sure. I think Brian or David would be much better people
> > to comment on this part.
> 
> I'm doing it the way fsl_quadspi.c does it.  It works on my Cyclone5
> test system with and without that 0002 patch.  So maybe I'll leave it
> out for now.

It indeed works, but that doesn't mean it is correct. The most simple test
to show you why I needed that 0002 patch would be for you to check if the
m25p,fast-read prop, which you are actually adding in this patchset to the
QSPI flash device, is set from within the spi-nor driver. It will never be
set because you're not passing the DT of_node pointer into the spi-nor driver.

> V5 patches on the way...

Thanks!

Best regards,
Marek Vasut

      reply	other threads:[~2015-07-24 20:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 13:36 [PATCH V4 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver Graham Moore
2015-03-23 13:36 ` [PATCH V4 2/2] mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller Graham Moore
2015-05-11 13:50   ` Graham Moore
2015-05-20 22:26   ` Brian Norris
2015-06-01 13:49     ` Graham Moore
2015-07-24 12:45 ` [PATCH V4 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver Marek Vasut
2015-07-24 16:12   ` Graham Moore
2015-07-24 16:25     ` Marek Vasut
2015-07-24 17:16       ` Graham Moore
2015-07-24 19:57         ` 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=201507242157.05840.marex@denx.de \
    --to=marex@denx.de \
    --cc=atull@opensource.altera.com \
    --cc=computersforpeace@gmail.com \
    --cc=dinguyen@opensource.altera.com \
    --cc=dwmw2@infradead.org \
    --cc=grmoore@opensource.altera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=yvanderv@opensource.altera.com \
    /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