From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: SHUKLA Mamta Ramendra <mamta.shukla@leica-geosystems.com>,
"pratyush@kernel.org" <pratyush@kernel.org>,
"michael@walle.cc" <michael@walle.cc>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: GEO-CHHER-bsp-development <bsp-development.geo@leica-geosystems.com>
Subject: Re: [PATCH v2] mtd: micron-st: enable lock/unlock for mt25qu512a
Date: Thu, 21 Sep 2023 15:35:51 +0100 [thread overview]
Message-ID: <4425afd4-c38c-4f27-96a6-9833fe2401b4@linaro.org> (raw)
In-Reply-To: <17989610-d069-40e2-9b4d-7ca6bdf2497e@linaro.org>
On 9/21/23 15:31, Tudor Ambarus wrote:
cut
>
> So the first commit will look like:
> diff --git a/drivers/mtd/spi-nor/micron-st.c
> b/drivers/mtd/spi-nor/micron-st.c
> index 4afcfc57c896..a8da1f18e335 100644
> --- a/drivers/mtd/spi-nor/micron-st.c
> +++ b/drivers/mtd/spi-nor/micron-st.c
> @@ -405,9 +405,6 @@ static const struct flash_info st_nor_parts[] = {
> }, {
> .id = SNOR_ID(0x20, 0xbb, 0x20, 0x10, 0x44, 0x00),
> .name = "mt25qu512a",
> - .size = SZ_64M,
> - .no_sfdp_flags = SECT_4K | SPI_NOR_DUAL_READ |
> SPI_NOR_QUAD_READ,
> - .fixup_flags = SPI_NOR_4B_OPCODES,
since we removed the 4b-opcodes flag here,
> .mfr_flags = USE_FSR,
> }, {
> .id = SNOR_ID(0x20, 0xbb, 0x20),
>
> and the second one will add just the BP support, something like:
> diff --git a/drivers/mtd/spi-nor/micron-st.c
> b/drivers/mtd/spi-nor/micron-st.c
> index a8da1f18e335..fdafbfa0f936 100644
> --- a/drivers/mtd/spi-nor/micron-st.c
> +++ b/drivers/mtd/spi-nor/micron-st.c
> @@ -405,6 +405,8 @@ static const struct flash_info st_nor_parts[] = {
> }, {
> .id = SNOR_ID(0x20, 0xbb, 0x20, 0x10, 0x44, 0x00),
> .name = "mt25qu512a",
> + .flags = SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB |
> SPI_NOR_4BIT_BP |
> + SPI_NOR_BP3_SR_BIT6,
> .mfr_flags = USE_FSR,
> }, {
> .id = SNOR_ID(0x20, 0xbb, 0x20),
>
> Of course, I expect you to run again the mtd_debug tests and also verify
> the locking. Thanks!
would also be good if you can also verify that 4BAIT SFDP table is
present and you still use the 4B opcodes after the change.
>
> Cheers,
> ta
>
next prev parent reply other threads:[~2023-09-21 17:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 15:49 Mamta Shukla
2023-07-06 6:42 ` Michael Walle
2023-07-13 3:43 ` Tudor Ambarus
2023-07-14 8:15 ` SHUKLA Mamta Ramendra
2023-08-22 12:16 ` SHUKLA Mamta Ramendra
2023-09-21 14:31 ` Tudor Ambarus
2023-09-21 14:35 ` Tudor Ambarus [this message]
2023-10-05 9:21 ` SHUKLA Mamta Ramendra
2023-10-05 13:51 ` Tudor Ambarus
2023-10-05 14:21 ` SHUKLA Mamta Ramendra
2023-10-05 14:59 ` Tudor Ambarus
2023-10-06 10:30 ` SHUKLA Mamta Ramendra
2023-10-06 13:33 ` Tudor Ambarus
2023-10-06 13:46 ` Tudor Ambarus
2023-10-06 16:09 ` SHUKLA Mamta Ramendra
2023-10-09 6:13 ` Tudor Ambarus
2023-10-16 9:39 ` SHUKLA Mamta Ramendra
2023-10-17 7:53 ` Tudor Ambarus
2023-10-17 13:53 ` SHUKLA Mamta Ramendra
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=4425afd4-c38c-4f27-96a6-9833fe2401b4@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=bsp-development.geo@leica-geosystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mamta.shukla@leica-geosystems.com \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--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
all inboxes | Powered by JetHome®