All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <dac2@pensando.io>, <linux-mtd@lists.infradead.org>, <vigneshr@ti.com>
Cc: snelson@pensando.io
Subject: Re: [PATCH 2/2] mtd: spi-nor: Support SPI_NOR_DUAL_READ on Micron mt25qu02g.
Date: Fri, 17 Jul 2020 10:33:35 +0000	[thread overview]
Message-ID: <1724beec-aceb-b6e9-1288-da340d3fd43c@microchip.com> (raw)
In-Reply-To: <20200716211631.38949-3-dac2@pensando.io>

On 7/17/20 12:16 AM, David Clear wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> The Micron mt25qu02g supports both x2 and x4 transactions.  Add the
> SPI_NOR_DUAL_READ to its spi_nor_ids[] table entry.

In spi_nor_select_read() we select the fastest read. Since this flash
supports Quad Read, the Dual Read will never get selected. As of now,
there is no benefit in adding SPI_NOR_DUAL_READ when SPI_NOR_QUAD_READ
is specified.

Both SPI_NOR_DUAL_READ and SPI_NOR_QUAD_READ trigger the parsing of
SFDP, maybe we should choose to add just the fastest SPI_NOR_*_READ
supported by the flash when declaring one. We would have to update
all the flash entries. Vignesh?

> 
> Signed-off-by: David Clear <dac2@pensando.io>
> Acked-by: Shannon Nelson <snelson@pensando.io>
> ---
>  drivers/mtd/spi-nor/micron-st.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/mtd/spi-nor/micron-st.c b/drivers/mtd/spi-nor/micron-st.c
> index 3dca5b9af3b6..ef3695080710 100644
> --- a/drivers/mtd/spi-nor/micron-st.c
> +++ b/drivers/mtd/spi-nor/micron-st.c
> @@ -71,8 +71,8 @@ static const struct flash_info st_parts[] = {
>                               SECT_4K | USE_FSR | SPI_NOR_QUAD_READ |
>                               NO_CHIP_ERASE) },
>         { "mt25qu02g",   INFO(0x20bb22, 0, 64 * 1024, 4096,
> -                             SECT_4K | USE_FSR | SPI_NOR_QUAD_READ |
> -                             NO_CHIP_ERASE) },
> +                             SECT_4K | USE_FSR | SPI_NOR_DUAL_READ |
> +                             SPI_NOR_QUAD_READ | NO_CHIP_ERASE) },
> 
>         { "m25p05",  INFO(0x202010,  0,  32 * 1024,   2, 0) },
>         { "m25p10",  INFO(0x202011,  0,  32 * 1024,   4, 0) },
> --
> 2.17.1
> 

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-07-17 10:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 21:16 [PATCH 0/2] Support flash devices used on Pensando boards David Clear
2020-07-16 21:16 ` [PATCH 1/2] mtd: spi-nor: Add support for Macronix mx66u2g45g David Clear
2020-07-17 10:38   ` Tudor.Ambarus
     [not found]     ` <CA+nMikGEEOoKri5z2T3Ms-3cEi+G014ha+rwrwZWeRn=DxfU9w@mail.gmail.com>
2020-07-17 16:44       ` Fwd: " David Clear
2020-07-16 21:16 ` [PATCH 2/2] mtd: spi-nor: Support SPI_NOR_DUAL_READ on Micron mt25qu02g David Clear
2020-07-17 10:33   ` Tudor.Ambarus [this message]
     [not found]     ` <CA+nMikFDWgLMAhb2rUZnAaLUJdimKZZxqKsQACnXrmCMb_CLMw@mail.gmail.com>
2020-07-17 16:42       ` Fwd: " David Clear
2020-07-17 18:00     ` David Clear
2020-07-18  5:35       ` Tudor.Ambarus
2020-07-18 17:23         ` David Clear

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=1724beec-aceb-b6e9-1288-da340d3fd43c@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=dac2@pensando.io \
    --cc=linux-mtd@lists.infradead.org \
    --cc=snelson@pensando.io \
    --cc=vigneshr@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.