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: Fri, 6 Oct 2023 14:33:11 +0100 [thread overview]
Message-ID: <f0a7acb3-00b5-433d-af5c-724a509fb816@linaro.org> (raw)
In-Reply-To: <eb2a9138-a76e-4b1e-e001-315149c4dabd@leica-geosystems.com>
Hi,
Thanks for the debugging info.
On 10/6/23 11:30, SHUKLA Mamta Ramendra wrote:
cut
> --------------------------------------------------------
>
> IMO, HAS_16BIT_SR flag is causing lock/unlock failure,
> since BP bits are calculated wrong then.
>
> I tested also for a case where I don't parse SFDP and
> reverted the condition in micron_st_nor_default_init()
> for 16BIT Status Register Flag. And lock/unlock fails with
> same log as Non-working case.
>
> And this mt25qu512 has 8-BIT SR as typical micron-st flash.
>
Indeed, the problem is that HAS_16BIT_SR gets set when it shouldn't have
to. This means that the BFPT table of the flash is wrong and we should
fix the parsed settings via a post_bfpt hook.
Does the following fix your problem?
diff --git a/drivers/mtd/spi-nor/micron-st.c
b/drivers/mtd/spi-nor/micron-st.c
index 4afcfc57c896..733bbddc6829 100644
--- a/drivers/mtd/spi-nor/micron-st.c
+++ b/drivers/mtd/spi-nor/micron-st.c
@@ -180,6 +180,17 @@ static const struct flash_info micron_nor_parts[] = {
},
};
+static int mt25qu512a_post_bfpt_fixup(struct spi_nor *nor,
+ const struct sfdp_parameter_header
*bfpt_header,
+ const struct sfdp_bfpt *bfpt)
+{
+ nor->flags &= ~SNOR_F_HAS_16BIT_SR;
+}
+
+static struct spi_nor_fixups mt25qu512a_fixups = {
+ .post_bfpt = mt25qu512a_post_bfpt_fixup,
+}
+
static const struct flash_info st_nor_parts[] = {
{
.name = "m25p05-nonjedec",
@@ -405,10 +416,10 @@ 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,
+ .flags = SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB |
SPI_NOR_4BIT_BP |
+ SPI_NOR_BP3_SR_BIT6,
.mfr_flags = USE_FSR,
+ .fixups = &mt25qu512a_fixups,
}, {
.id = SNOR_ID(0x20, 0xbb, 0x20),
.name = "n25q512a",
If yes, please add some prints in sfdp.c to determine where it's set,
either in BFPT_DWORD15_QER_SR2_BIT1 or BFPT_DWORD15_QER_SR2_BIT1_NO_RD
Is the datasheet for this flash public? Would you send me a link to it
please?
Cheers,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-10-06 13:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 15:49 [PATCH v2] mtd: micron-st: enable lock/unlock for mt25qu512a 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
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 [this message]
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=f0a7acb3-00b5-433d-af5c-724a509fb816@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;
as well as URLs for NNTP newsgroup(s).