From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Liu Xiang <liu.xiang6@zte.com.cn>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
marek.vasut@gmail.com, dwmw2@infradead.org,
computersforpeace@gmail.com, richard@nod.at,
liuxiang_1999@126.com,
Tudor Ambarus <tudor.ambarus@microchip.com>
Subject: Re: [PATCH] mtd: spi-nor: Return error when nor->addr_width not match the device size
Date: Wed, 14 Nov 2018 14:51:29 +0100 [thread overview]
Message-ID: <20181114145129.568e4bb3@bbrezillon> (raw)
In-Reply-To: <1542200165-3073-1-git-send-email-liu.xiang6@zte.com.cn>
On Wed, 14 Nov 2018 20:56:05 +0800
Liu Xiang <liu.xiang6@zte.com.cn> wrote:
> In is25lp256, the DWORD1 of JEDEC Basic Flash Parameter Header
> is 0xfff920e5. So the DWORD1[18:17] Address Bytes bits are 0b00,
> means that 3-Byte only addressing.
According to your other patch this NOR supports 4B opcode, which means
the SFDP table is wrong.
> But the device size is larger
> than 16MB, nor->addr_width must be 4 to access the whole address.
> An error should be returned when nor->addr_width not match
^does not
> the device size in spi_nor_parse_sfdp().
>
> Suggested-by: Boris Brezillon <boris.brezillon@bootlin.com>
> Signed-off-by: Liu Xiang <liu.xiang6@zte.com.cn>
> ---
> drivers/mtd/spi-nor/spi-nor.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index 3eba13a..77eaf22 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -2669,6 +2669,10 @@ static int spi_nor_parse_bfpt(struct spi_nor *nor,
> }
> params->size >>= 3; /* Convert to bytes. */
>
> + /*if the device exceeds 16MiB, addr_width must be 4*/
Please add a white space after '/*' and before '*/':
/* If the device exceeds 16MiB, ->addr_width must be 4. */
> + if ((params->size > 0x1000000) && (nor->addr_width == 3))
Parens are not needed around sub-conditions:
if (params->size > 0x1000000 && nor->addr_width == 3)
> + return -EINVAL;
> +
I'm not sure this is correct. Looks like some NORs only support 3B
opcodes but have a "4-byte addressing" mode (see set_4byte() [1]).
Don't know what's reported by the BFPT section in this case though
(BFPT_DWORD1_ADDRESS_BYTES_3_ONLY or BFPT_DWORD1_ADDRESS_BYTES_3_OR_4).
Anyway, I think this check should be moved here [2] to cover the
non-SFDP case.
> /* Fast Read settings. */
> for (i = 0; i < ARRAY_SIZE(sfdp_bfpt_reads); i++) {
> const struct sfdp_bfpt_read *rd = &sfdp_bfpt_reads[i];
[1]https://elixir.bootlin.com/linux/v4.20-rc2/source/drivers/mtd/spi-nor/spi-nor.c#L278
[2]https://elixir.bootlin.com/linux/v4.20-rc2/source/drivers/mtd/spi-nor/spi-nor.c#L3758
next prev parent reply other threads:[~2018-11-14 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 12:56 [PATCH] mtd: spi-nor: Return error when nor->addr_width not match the device size Liu Xiang
2018-11-14 13:51 ` Boris Brezillon [this message]
2018-11-14 14:46 ` Liu Xiang
2018-11-15 10:54 ` Tudor.Ambarus
2018-11-15 11:02 ` Boris Brezillon
2018-11-16 13:24 ` Liu Xiang
2019-03-13 13:20 ` Liu Xiang
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=20181114145129.568e4bb3@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=liu.xiang6@zte.com.cn \
--cc=liuxiang_1999@126.com \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.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