All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Huang Shijie <shijie8@gmail.com>
Cc: angus.clark@st.com, Huang Shijie <b32955@freescale.com>,
	linux-mtd@lists.infradead.org, sourav.poddar@ti.com,
	computersforpeace@gmail.com, dwmw2@infradead.org
Subject: Re: [RFC PATCH] mtd: spi-nor: add DDR quad read support
Date: Mon, 21 Apr 2014 17:26:07 +0200	[thread overview]
Message-ID: <201404211726.07963.marex@denx.de> (raw)
In-Reply-To: <20140417160515.GB14819@localhost.localdomain>

On Thursday, April 17, 2014 at 06:05:17 PM, Huang Shijie wrote:
> On Thu, Apr 17, 2014 at 04:24:36PM +0200, Marek Vasut wrote:
> > On Wednesday, April 16, 2014 at 11:47:21 AM, Huang Shijie wrote:
> > [...]
> > 
> > > @@ -74,6 +74,11 @@ static int read_cr(struct spi_nor *nor)
> > > 
> > >  static inline int spi_nor_read_dummy_cycles(struct spi_nor *nor)
> > >  {
> > >  
> > >  	switch (nor->flash_read) {
> > > 
> > > +	case SPI_NOR_DDR_QUAD:
> > > +		/*
> > > +		 * We set 8 for the DDR Quad read, the SPI NOR controller
> > > +		 * can change it to 6 or 4 with DeviceTree property.
> > > +		 */
> > 
> > Isn't the number of dummy cycles a property of the chip ?
> 
> I want to add DT node, such as "ddr_quad_read_dummy".
> But I do not know which Document file to put the DT node to.
> 
> the spi-bus.txt ? or the spi-nor.txt?

It's a property of the chip, therefore spi-nor.txt , no ?
[...]

I replied about the failing-to-lower-mode in the other email.

Best regards,
Marek Vasut

  reply	other threads:[~2014-04-21 21:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16  9:47 [RFC PATCH] mtd: spi-nor: add DDR quad read support Huang Shijie
2014-04-17 14:24 ` Marek Vasut
2014-04-17 16:05   ` Huang Shijie
2014-04-21 15:26     ` Marek Vasut [this message]
2014-04-22  7:33       ` Huang Shijie
2014-04-17 18:41   ` Geert Uytterhoeven
2014-04-21 15:25     ` Marek Vasut

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=201404211726.07963.marex@denx.de \
    --to=marex@denx.de \
    --cc=angus.clark@st.com \
    --cc=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shijie8@gmail.com \
    --cc=sourav.poddar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.