From: Marek Vasut <marex@denx.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: angus.clark@st.com, Huang Shijie <b32955@freescale.com>,
MTD Maling List <linux-mtd@lists.infradead.org>,
Sourav Poddar <sourav.poddar@ti.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC PATCH] mtd: spi-nor: add DDR quad read support
Date: Mon, 21 Apr 2014 17:25:04 +0200 [thread overview]
Message-ID: <201404211725.04505.marex@denx.de> (raw)
In-Reply-To: <CAMuHMdVY_n88uR7zOAZTo_V7Sg5zzaUFQjdaTSZeVj6Jbh0Txw@mail.gmail.com>
On Thursday, April 17, 2014 at 08:41:50 PM, Geert Uytterhoeven wrote:
> On Thu, Apr 17, 2014 at 4:24 PM, Marek Vasut <marex@denx.de> wrote:
> >> @@ -1016,8 +1038,15 @@ int spi_nor_scan(struct spi_nor *nor, const
> >> struct spi_device_id *id, if (info->flags & SPI_NOR_NO_FR)
> >>
> >> nor->flash_read = SPI_NOR_NORMAL;
> >>
> >> - /* Quad/Dual-read mode takes precedence over fast/normal */
> >> - if (mode == SPI_NOR_QUAD && info->flags & SPI_NOR_QUAD_READ) {
> >> + /* DDR Quad/Quad/Dual-read mode takes precedence over fast/normal
> >> */ + if (mode == SPI_NOR_DDR_QUAD && info->flags &
> >> SPI_NOR_DDR_QUAD_READ) { + ret = set_ddr_quad_mode(nor,
> >> info->jedec_id);
> >> + if (ret) {
> >> + dev_err(dev, "DDR quad mode not supported\n");
> >> + return ret;
> >
> > Is it really necessary to fail here? Can we not fall back to some "lower"
> > mode ?
>
> IIRC, the original m25p80 also fails, FWIW...
OK, so let's keep consistent. But maybe we should add a note for future
generations that this can be improved.
Best regards,
Marek Vasut
prev parent 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
2014-04-22 7:33 ` Huang Shijie
2014-04-17 18:41 ` Geert Uytterhoeven
2014-04-21 15:25 ` 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=201404211725.04505.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=geert@linux-m68k.org \
--cc=linux-mtd@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox