From: <Takahiro.Kuwano@infineon.com>
To: <jim.t90615@gmail.com>, <JJLIU0@nuvoton.com>,
<trini@konsulko.com>, <vigneshr@ti.com>, <dhphadke@microsoft.com>
Cc: <u-boot@lists.denx.de>, <u-boot@lists.u-boot-project.org>
Subject: RE: [PATCH 2/2] mtd: spi-nor-ids: add GigaDevice GD25LB512MF
Date: Thu, 24 Sep 2026 01:58:29 +0000 [thread overview]
Message-ID: <c94b42e4eae94a5585e8afa7fbf2b526@infineon.com> (raw)
In-Reply-To: <20260918024842.1838692-1-JJLIU0@nuvoton.com>
Hi,
> Add the 64MB GD25LB512MF (JEDEC ID 0xc8601a) to the SPI NOR ID table.
>
Please confirm the datasheet link [1], and add Link: tag.
> Signed-off-by: Jim Liu <JJLIU0@nuvoton.com>
> ---
> drivers/mtd/spi/spi-nor-ids.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c
> index 3e7096bd419..06794d5507a 100644
> --- a/drivers/mtd/spi/spi-nor-ids.c
> +++ b/drivers/mtd/spi/spi-nor-ids.c
> @@ -187,6 +187,8 @@ const struct flash_info spi_nor_ids[] = {
> SPI_NOR_QUAD_READ | SPI_NOR_HAS_LOCK | SPI_NOR_4B_OPCODES)},
> {INFO("gd25lb512", 0xc8671A, 0, 64 * 1024, 1024, SECT_4K |
> SPI_NOR_QUAD_READ | SPI_NOR_HAS_LOCK | SPI_NOR_4B_OPCODES)},
> + {INFO("gd25lb512mf", 0xc8601A, 0, 64 * 1024, 1024, SECT_4K |
> + SPI_NOR_QUAD_READ | SPI_NOR_HAS_LOCK | SPI_NOR_4B_OPCODES)},
The chip has 4-bit BP and TB that not supported in u-boot.
Probably the other existing chips have the same issue, but I'm reluctant to
add a new chip with HAS_LOCK flag when it is known not to work...
Thanks,
Takahiro
> {INFO("gd55lb01g", 0xc8671B, 0, 64 * 1024, 2048, SECT_4K |
> SPI_NOR_QUAD_READ | SPI_NOR_HAS_LOCK | SPI_NOR_4B_OPCODES)},
> {INFO("gd55lb02g", 0xc8671C, 0, 64 * 1024, 4096, SECT_4K |
> --
> 2.34.1
[1] https://download.gigadevice.com/Datasheet/DS-01014-GD25LB512MF-Rev1.1.pdf
prev parent reply other threads:[~2026-09-24 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 2:48 [PATCH 2/2] mtd: spi-nor-ids: add GigaDevice GD25LB512MF Jim Liu
2026-09-24 1:58 ` Takahiro.Kuwano [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=c94b42e4eae94a5585e8afa7fbf2b526@infineon.com \
--to=takahiro.kuwano@infineon.com \
--cc=JJLIU0@nuvoton.com \
--cc=dhphadke@microsoft.com \
--cc=jim.t90615@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-boot@lists.u-boot-project.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