From: Anshul Dalal <anshuld@ti.com>
To: Ssunk <ssunkkan@gmail.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Vignesh R <vigneshr@ti.com>
Cc: <u-boot@lists.denx.de>
Subject: Re: [PATCH] mtd: spi-nor: ids: Add support for Puyasemi flash chips
Date: Mon, 2 Feb 2026 11:12:29 +0530 [thread overview]
Message-ID: <DG48IKMSA1IL.2D1LC7O9QABVJ@ti.com> (raw)
In-Reply-To: <20260130110132.8018-1-ssunkkan@gmail.com>
On Fri Jan 30, 2026 at 4:31 PM IST, Ssunk wrote:
> This patch adds JEDEC IDs for Puyasemi PY25F512HB, PY25F01GHB,
> PY25F512LC, and PY25F01GLC flash parts.
>
> site: https://www.puyasemi.com
A link to the datasheets and a reference to the "Table ID Definitions"
would be helpful in cross-checking the correctness of the IDs.
>
> Signed-off-by: Ssunk <ssunkkan@gmail.com>
The patch doesn't apply cleanly, please rebase on master or next (as
appropriate) for the next revision.
> ---
> drivers/mtd/spi/Kconfig | 6 ++++++
> drivers/mtd/spi/spi-nor-ids.c | 11 +++++++++++
> 2 files changed, 17 insertions(+)
>
> diff --git a/drivers/mtd/spi/Kconfig b/drivers/mtd/spi/Kconfig
> index a9617c6c58..c223862a46 100644
> --- a/drivers/mtd/spi/Kconfig
> +++ b/drivers/mtd/spi/Kconfig
> @@ -217,6 +217,12 @@ config SPI_FLASH_XTX
> Add support for various XTX (XTX Technology Limited)
> SPI flash chips (XT25xxx).
>
> +config SPI_FLASH_PUYASEMI
> + bool "PUYASEMI SPI flash support"
> + help
> + Add support for various PUYASEMI (Puya Semiconductor (Shanghai) Co., Ltd.)
> + SPI flash chips (py25xxx)
> +
Can't this be included as part of the existing CONFIG_SPI_FLASH_PUYA
which was added by the commit 5c73c05f20be ("mtd: spi-nor-ids: Add Puya
Semiconductor chips description")?
Nit: Would be nice to see new configs being added in alphabetical order
in the Kconfig, though the order is not strictly followed currently :(
> endif
>
> config SPI_FLASH_USE_4K_SECTORS
> diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c
> index 4b7b358eac..2e479ab8a1 100644
> --- a/drivers/mtd/spi/spi-nor-ids.c
> +++ b/drivers/mtd/spi/spi-nor-ids.c
> @@ -624,6 +624,17 @@ const struct flash_info spi_nor_ids[] = {
> SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> { INFO("xt25w01g", 0x0b651B, 0, 64 * 1024, 2048,
> SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> +#endif
> +#ifdef CONFIG_SPI_FLASH_PUYASEMI
> + /* Puya Semiconductor (Shanghai) Co., Ltd */
> + { INFO("py25f512hb", 0x85231a, 0, 64 * 1024, 1024,
> + SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> + { INFO("py25f01ghb", 0x85231b, 0, 64 * 1024, 2048,
> + SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> + { INFO("py25f512lc", 0x85631a, 0, 64 * 1024, 1024,
> + SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> + { INFO("py25f01glc", 0x85631b, 0, 64 * 1024, 2048,
> + SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> #endif
> { },
> };
next prev parent reply other threads:[~2026-02-02 5:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 11:01 [PATCH] mtd: spi-nor: ids: Add support for Puyasemi flash chips Ssunk
2026-02-02 5:42 ` Anshul Dalal [this message]
2026-02-04 14:07 ` Clus Tom
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=DG48IKMSA1IL.2D1LC7O9QABVJ@ti.com \
--to=anshuld@ti.com \
--cc=jagan@amarulasolutions.com \
--cc=ssunkkan@gmail.com \
--cc=u-boot@lists.denx.de \
--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