From: Boris Brezillon <boris.brezillon@bootlin.com>
To: <Tudor.Ambarus@microchip.com>
Cc: <alexandre.belloni@bootlin.com>, <richard@nod.at>,
<marek.vasut@gmail.com>, <linux-mtd@lists.infradead.org>,
<alexander.sverdlin@nokia.com>, <computersforpeace@gmail.com>,
<dwmw2@infradead.org>
Subject: Re: [PATCH v4 1/3] mtd: spi-nor: Add the SNOR_F_4B_OPCODES flag
Date: Wed, 5 Dec 2018 17:00:25 +0100 [thread overview]
Message-ID: <20181205170025.0ccb8837@bbrezillon> (raw)
In-Reply-To: <1f244544-7f85-fa28-afcd-d6b7fae192fe@microchip.com>
On Wed, 5 Dec 2018 15:48:46 +0000
<Tudor.Ambarus@microchip.com> wrote:
> On 12/05/2018 05:19 PM, Boris Brezillon wrote:
> >>> @@ -3750,6 +3747,10 @@ int spi_nor_scan(struct spi_nor *nor, const char *name,
> >>> if (info->flags & SPI_NOR_NO_FR)
> >>> params.hwcaps.mask &= ~SNOR_HWCAPS_READ_FAST;
> >>>
> >>> + if (info->flags & SPI_NOR_4B_OPCODES ||
> >>> + (JEDEC_MFR(info) == SNOR_MFR_SPANSION && mtd->size > SZ_16M))
> >>> + nor->flags |= SNOR_F_4B_OPCODES;
> >>> +
> >> you are potentially overwriting the SNOR_F_4B_OPCODES that may be set in SFDP. I
> >> suggest to set SNOR_F_4B_OPCODES flag inside of the "if (mtd->size > 0x1000000)"
> >> block.
> > Shouldn't we override this value anyway? I mean, I thought flash_info
> > flags had precedence on the SFDP ones. Also, just because the flash is
>
> I tend to say that we shouldn't. We have some "JEDEC knows better" attitude in
> the code: we are overwriting platform ID if we find a different ID in sfdp, we
> choose addr_width from SFDP even if set in info->addr_width, and we are
> overwriting all the settings based on flash_info when sfdp parsing succeeds in
> spi_nor_init_params().
Given all the "broken SFDP" problems we had, I'm not sure this was the
right decision, but that's another topic.
For this specific one, I'd really prefer to keep this code as is. Note
that the "JEDEC_MFR(info) == SNOR_MFR_SPANSION && mtd->size > SZ_16M"
is later moved to a post SFDP fixup hook in my rework, which means we'll
anyway override the decision taken by the SFDP parsing.
>
> > smaller than 16MB, doesn't mean it does not support 4B opcodes. We
> > probably won't use the 4B opcodes in that case, but still.
> >
>
> I agree that manufacturers have a sense of humor and this might be possible. But
> there's no need to use 4B opcodes in this case, so a post_sfdp fixup will help
> here too.
Except there's nothing to fix in this case, we just won't use 4B
opcodes if we don't need to, that's all.
next prev parent reply other threads:[~2018-12-05 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 14:41 [PATCH v4 0/3] mtd: spi-nor: mx25l25635f: Use 4B opcodes Boris Brezillon
2018-11-29 14:41 ` [PATCH v4 1/3] mtd: spi-nor: Add the SNOR_F_4B_OPCODES flag Boris Brezillon
2018-12-05 15:08 ` Tudor.Ambarus
2018-12-05 15:19 ` Boris Brezillon
2018-12-05 15:48 ` Tudor.Ambarus
2018-12-05 16:00 ` Boris Brezillon [this message]
2018-12-05 16:26 ` Tudor.Ambarus
2018-12-05 16:32 ` Boris Brezillon
2018-12-05 16:54 ` Boris Brezillon
2018-11-29 14:41 ` [PATCH v4 2/3] mtd: spi-nor: Add a post BFPT parsing fixup hook Boris Brezillon
2018-12-05 16:35 ` Tudor.Ambarus
2018-12-05 16:47 ` Boris Brezillon
2018-12-06 10:25 ` Boris Brezillon
2018-11-29 14:41 ` [PATCH v4 3/3] mtd: spi-nor: Add a post BFPT fixup for MX25L25635E Boris Brezillon
2018-12-05 16:41 ` Tudor.Ambarus
2018-12-05 16:50 ` Boris Brezillon
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=20181205170025.0ccb8837@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=alexander.sverdlin@nokia.com \
--cc=alexandre.belloni@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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).