From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Mamta Shukla <mamta.shukla@leica-geosystems.com>,
pratyush@kernel.org, michael@walle.cc, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: bsp-development.geo@leica-geosystems.com
Subject: Re: [PATCH v2] mtd: micron-st: enable lock/unlock for mt25qu512a
Date: Thu, 13 Jul 2023 06:43:57 +0300 [thread overview]
Message-ID: <19800e51-a871-be9f-9eb5-5829237e2613@linaro.org> (raw)
In-Reply-To: <20230705154942.3936658-1-mamta.shukla@leica-geosystems.com>
On 05.07.2023 18:49, Mamta Shukla wrote:
> mt25qu512a[1] supports locking/unlocking through BP bits in SR.
>
> Tested using mtd-utils- flash_lock/flash_unlock for MT25QU512ABB8E12.
>
> Link: https://media-www.micron.com/-/media/client/global/documents/products/data-sheet/nor-flash/serial-nor/mt25q/die-rev-b/mt25q_qlkt_u_512_abb_0.pdf?rev=b259aadc3bea49ea8210a41c9ad58211
> Signed-off-by: Mamta Shukla <mamta.shukla@leica-geosystems.com>
> ---
> Changes in v2:
> - add Link tag
> - fix chip part number mt25ql512a->mt25qu512a
>
> drivers/mtd/spi-nor/micron-st.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/micron-st.c b/drivers/mtd/spi-nor/micron-st.c
> index 4b919756a205..08e94340ebaa 100644
> --- a/drivers/mtd/spi-nor/micron-st.c
> +++ b/drivers/mtd/spi-nor/micron-st.c
> @@ -229,6 +229,8 @@ static const struct flash_info st_nor_parts[] = {
> MFR_FLAGS(USE_FSR)
> },
> { "mt25qu512a", INFO6(0x20bb20, 0x104400, 64 * 1024, 1024)
> + FLAGS(SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB | SPI_NOR_4BIT_BP |
> + SPI_NOR_BP3_SR_BIT6)
> NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ)
> FIXUP_FLAGS(SPI_NOR_4B_OPCODES)
> MFR_FLAGS(USE_FSR)
Can you try the following instead? We try to use SFDP parsing whenever
possible.
{ "mt25qu512a", INFO6(0x20bb20, 0x104400, 0, 0)
FLAGS(SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB | SPI_NOR_4BIT_BP |
SPI_NOR_BP3_SR_BIT6)
PARSE_SFDP
MFR_FLAGS(USE_FSR)
You then have to dump the SFDP tables and do a sanity check to make sure
everything's fine after your changes. You can an example on how to do
that on the commit message from
https://lore.kernel.org/linux-mtd/8b7d2420-26b6-405b-8ef7-75e0a0201402@linaro.org/T/#m3550973e0884ec4a288d344fabd4a9c3b64af46e
next prev parent reply other threads:[~2023-07-13 3:44 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 [this message]
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
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=19800e51-a871-be9f-9eb5-5829237e2613@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®