From: <Tudor.Ambarus@microchip.com>
To: <cleger@kalray.eu>
Cc: <miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: Add support for is25lp01g
Date: Mon, 20 Apr 2020 12:14:31 +0000 [thread overview]
Message-ID: <1950407.5XCTmqoEVg@192.168.0.120> (raw)
In-Reply-To: <20200417160839.25880-1-cleger@kalray.eu>
Hi, Clement,
On Friday, April 17, 2020 7:08:39 PM EEST Clement Leger wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Update the issi_parts table for is25lp01g (128MB) device from ISSI.
> Tested on Kalray K200 board.
>
> Signed-off-by: Clement Leger <cleger@kalray.eu>
> ---
> drivers/mtd/spi-nor/issi.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/issi.c b/drivers/mtd/spi-nor/issi.c
> index ffcb60e54a80..c3c3438e3d08 100644
> --- a/drivers/mtd/spi-nor/issi.c
> +++ b/drivers/mtd/spi-nor/issi.c
> @@ -49,6 +49,8 @@ static const struct flash_info issi_parts[] = {
> SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ
> | SPI_NOR_4B_OPCODES)
> .fixups = &is25lp256_fixups },
> + { "is25lp01g", INFO(0x9d601b, 0, 64 * 1024, 2048,
There is a "K" flavor of this flash which has 512 Byte Page size with 256 KB
Block size. While the page size can be determined by parsing SFDP, I think we
will have some problems with sector_size because as of now, the sector_size is
always set to 64KB. An incorrect sector_size will affect erases and locking.
Cheers,
ta
next prev parent reply other threads:[~2020-04-20 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 16:08 [PATCH] mtd: spi-nor: Add support for is25lp01g Clement Leger
2020-04-20 12:14 ` Tudor.Ambarus [this message]
2020-04-20 14:50 ` Clément Leger
2020-04-21 4:40 ` Tudor.Ambarus
2020-04-21 7:07 ` Clément Leger
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=1950407.5XCTmqoEVg@192.168.0.120 \
--to=tudor.ambarus@microchip.com \
--cc=cleger@kalray.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox