From: Fabio Estevam <festevam@gmail.com>
To: michael@walle.cc
Cc: tudor.ambarus@linaro.org, pratyush@kernel.org,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
linux-mtd@lists.infradead.org, Fabio Estevam <festevam@denx.de>
Subject: [PATCH] mtd: spi-nor: micron-st: Add support for mt25qu01g
Date: Mon, 23 Oct 2023 18:38:00 -0300 [thread overview]
Message-ID: <20231023213800.2599704-1-festevam@gmail.com> (raw)
From: Fabio Estevam <festevam@denx.de>
Add support for the MT25QU01G 128MB Micron Serial NOR Flash Memory
model.
Datasheet:
https://www.micron.com/-/media/client/global/documents/products/data-sheet/nor-flash/serial-nor/mt25q/die-rev-b/mt25q_qlkt_u_01g_bbb_0.pdf
Tested on a i.MX8MP based board:
# dmesg | grep spi-nor
[ 1.854474] spi-nor spi0.0: mt25qu01g (131072 Kbytes)
# cat /proc/mtd
dev: size erasesize name
mtd0: 08000000 00001000 "30bb0000.spi"
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
drivers/mtd/spi-nor/micron-st.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/mtd/spi-nor/micron-st.c b/drivers/mtd/spi-nor/micron-st.c
index 8920547c12bf..da2f8992bbc0 100644
--- a/drivers/mtd/spi-nor/micron-st.c
+++ b/drivers/mtd/spi-nor/micron-st.c
@@ -429,6 +429,13 @@ static const struct flash_info st_nor_parts[] = {
SPI_NOR_BP3_SR_BIT6,
.no_sfdp_flags = SECT_4K | SPI_NOR_QUAD_READ,
.mfr_flags = USE_FSR,
+ }, {
+ .id = SNOR_ID(0x20, 0xbb, 0x21, 0x10, 0x44, 0x00),
+ .name = "mt25qu01g",
+ .size = SZ_128M,
+ .flags = NO_CHIP_ERASE,
+ .no_sfdp_flags = SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ,
+ .mfr_flags = USE_FSR,
}, {
.id = SNOR_ID(0x20, 0xbb, 0x21),
.name = "n25q00a",
--
2.34.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2023-10-23 21:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 21:38 Fabio Estevam [this message]
2023-10-24 6:01 ` [PATCH] mtd: spi-nor: micron-st: Add support for mt25qu01g Tudor Ambarus
2023-10-24 13:57 ` Fabio Estevam
2023-10-24 14:23 ` Tudor Ambarus
2023-10-24 9:26 ` Michael Walle
2023-10-24 11:43 ` Fabio Estevam
2023-10-24 13:59 ` Michael Walle
2023-10-24 15:47 ` Fabio Estevam
2023-10-24 15:53 ` Tudor Ambarus
2023-10-24 16:20 ` Fabio Estevam
2023-10-24 16:36 ` Michael Walle
2023-10-24 16:43 ` Fabio Estevam
2023-10-25 3:34 ` Tudor Ambarus
2023-10-25 11:56 ` Fabio Estevam
2023-10-25 17:35 ` Fabio Estevam
2023-10-26 6:33 ` Michael Walle
2023-10-26 11:25 ` Fabio Estevam
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=20231023213800.2599704-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=festevam@denx.de \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--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