summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVincent Jardin <vjardin@free.fr>2026-05-20 17:00:21 +0200
committerTom Rini <trini@konsulko.com>2026-07-01 12:42:41 -0600
commite800cc67f5b6cb50a20f37c993ec1cd4063bdbd3 (patch)
tree40832ba5018152abe0ecd1458e6a4c494057c735
parent3900903a588964555c9e76cca53ada7d217c00f7 (diff)
downloadu-boot-e800cc67f5b6cb50a20f37c993ec1cd4063bdbd3.tar.gz
u-boot-e800cc67f5b6cb50a20f37c993ec1cd4063bdbd3.zip
mtd: spi-nor: Add gd55lb02gf chips
Add the GigaDevice GD55LB02GF (256 Mo) similar to gd55lb02ge with the same read path flags. SPI_NOR_HAS_LOCK and SPI_NOR_HAS_TB do not match this chip's status register layout: the GD55LB02GF uses a 5-bit block protect field BP0..BP4 plus a CMP bit in SR2 for direction (see datasheet "Status Register Block Protection"). The generic stm-lock helpers drive only BP0..BP2 and assume SR1 bit 5 is TB, but on this part SR1 bit 5 is BP3. Enabling either flag would leave BP3..BP4 unmanaged or corrupt BP3 on every lock op. A proper support needs a vendor specific lock callback, it is out of scope for this table update. Signed-off-by: Vincent Jardin <vjardin@free.fr> Suggested-by: Takahiro Kuwano <Takahiro.Kuwano@infineon.com> Reviewed-by: Takahiro Kuwano <takahiro.kuwano@infineon.com>
-rw-r--r--drivers/mtd/spi/spi-nor-ids.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c
index c0fa98424aa..31a2ba49a87 100644
--- a/drivers/mtd/spi/spi-nor-ids.c
+++ b/drivers/mtd/spi/spi-nor-ids.c
@@ -231,6 +231,10 @@ const struct flash_info spi_nor_ids[] = {
SECT_4K | SPI_NOR_QUAD_READ |
SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB)
},
+ {
+ INFO("gd55lb02gf", 0xc8601c, 0, 64 * 1024, 4096,
+ SECT_4K | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES)
+ },
#endif
#ifdef CONFIG_SPI_FLASH_ISSI /* ISSI */
/* ISSI */