From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Jakub Czapiga <czapiga@google.com>
Cc: Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: macronix: add MX77U25650F, MX77U25655F and MX77U51250F
Date: Tue, 18 Mar 2025 08:30:57 +0200 [thread overview]
Message-ID: <b3065eda-e224-48e5-a5fe-2d5c8f4e5b6c@linaro.org> (raw)
In-Reply-To: <20250317182058.2060277-1-czapiga@google.com>
On 17.03.2025 20:20, Jakub Czapiga wrote:
> MX77U25650F and MX77U25655F are 256Mbit chips with SFDP and block
> protection support. MX77U51250F is 512Mbit chip with SFDP and block
> protection support.
> All chips also support top-bottom lock configuration, however this bit
> is SR2(3) and is also OTP (defaults to top). Due to lack of API to
> support TB in SR2(3) and due to it being OTP these chips will only
> support top blocks protection.
>
> Signed-off-by: Jakub Czapiga <czapiga@google.com>
> ---
> drivers/mtd/spi-nor/macronix.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/spi-nor/macronix.c b/drivers/mtd/spi-nor/macronix.c
> index 99936fd25d43..c65e7cdab5cf 100644
> --- a/drivers/mtd/spi-nor/macronix.c
> +++ b/drivers/mtd/spi-nor/macronix.c
> @@ -193,7 +193,22 @@ static const struct flash_info macronix_nor_parts[] = {
> .name = "mx25l3255e",
> .size = SZ_4M,
> .no_sfdp_flags = SECT_4K,
> - },
> + }, {
> + .id = SNOR_ID(0xc2, 0x75, 0x39),
> + .name = "mx77u25650f",
> + .size = SZ_32M,
> + .flags = SPI_NOR_HAS_LOCK | SPI_NOR_4BIT_BP,
> + }, {
> + .id = SNOR_ID(0xc2, 0x76, 0x39),
> + .name = "mx77u25655f",
> + .size = SZ_32M,
> + .flags = SPI_NOR_HAS_LOCK | SPI_NOR_4BIT_BP,
> + }, {
> + .id = SNOR_ID(0xc2, 0x75, 0x3a),
> + .name = "mx77u51250f",
> + .size = SZ_64M,
> + .flags = SPI_NOR_HAS_LOCK | SPI_NOR_4BIT_BP,
drop name and size, add name as a comment and do the tests for the next
version.
> + }
> /*
> * This spares us of adding new flash entries for flashes that can be
> * initialized solely based on the SFDP data, but still need the
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2025-03-18 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 18:20 [PATCH] mtd: spi-nor: macronix: add MX77U25650F, MX77U25655F and MX77U51250F Jakub Czapiga
2025-03-18 6:30 ` Tudor Ambarus [this message]
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=b3065eda-e224-48e5-a5fe-2d5c8f4e5b6c@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=czapiga@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--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