From: "Michael Walle" <mwalle@kernel.org>
To: "Matthew Parker" <mparker@arista.com>, <pratyush@kernel.org>,
<miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, "Adam Calabrigo" <adamc@arista.com>
Subject: Re: [PATCH] mtd: spi-nor: gigadevice: Add support for GigaDevice GD25B512
Date: Mon, 09 Nov 2026 09:51:34 +0100 [thread overview]
Message-ID: <DMQJVVTSK5MO.2VQC80RTHL9LN@kernel.org> (raw)
In-Reply-To: <20261108022011.898185-1-mparker@arista.com>
[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]
Hi Matthew,
On Sun Nov 8, 2026 at 3:20 AM CET, Matthew Parker wrote:
> Add support for the GigaDevice GD25B512 512Mbit (64 MiB) SPI NOR flash.
>
> The chip exposes valid JESD216B SFDP tables including 4-byte address
> instruction tables, from which geometry and opcodes are discovered.
> Stateless 4-byte opcodes and status register locking are enabled. Read,
> write, and erase functionality across the full memory array have been
> tested on hardware.
>
> Cc: stable@vger.kernel.org # v6.1+
> Co-developed-by: Adam Calabrigo <adamc@arista.com>
Co-developed-by for just adding an id?
Please note that we have some requirements for new flashes, see [1].
Same for the your other patch.
-michael
[1] https://docs.kernel.org/driver-api/mtd/spi-nor.html
> Signed-off-by: Adam Calabrigo <adamc@arista.com>
> Signed-off-by: Matthew Parker <mparker@arista.com>
> ---
> drivers/mtd/spi-nor/gigadevice.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/gigadevice.c b/drivers/mtd/spi-nor/gigadevice.c
> index 6a2e6ebda148..de96cefde516 100644
> --- a/drivers/mtd/spi-nor/gigadevice.c
> +++ b/drivers/mtd/spi-nor/gigadevice.c
> @@ -64,6 +64,10 @@ static const struct flash_info gigadevice_nor_parts[] = {
> .id = SNOR_ID(0xc8, 0x40, 0x19),
> .name = "gd25q256",
> .flags = SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB | SPI_NOR_TB_SR_BIT6,
> + }, {
> + .id = SNOR_ID(0xc8, 0x47, 0x1a),
> + .flags = SPI_NOR_HAS_LOCK,
> + .fixup_flags = SPI_NOR_4B_OPCODES,
> }, {
> .id = SNOR_ID(0xc8, 0x60, 0x16),
> .name = "gd25lq32",
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Walle" <mwalle@kernel.org>
To: "Matthew Parker" <mparker@arista.com>, <pratyush@kernel.org>,
<miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, "Adam Calabrigo" <adamc@arista.com>
Subject: Re: [PATCH] mtd: spi-nor: gigadevice: Add support for GigaDevice GD25B512
Date: Mon, 09 Nov 2026 09:51:34 +0100 [thread overview]
Message-ID: <DMQJVVTSK5MO.2VQC80RTHL9LN@kernel.org> (raw)
In-Reply-To: <20261108022011.898185-1-mparker@arista.com>
[-- Attachment #1.1: Type: text/plain, Size: 1604 bytes --]
Hi Matthew,
On Sun Nov 8, 2026 at 3:20 AM CET, Matthew Parker wrote:
> Add support for the GigaDevice GD25B512 512Mbit (64 MiB) SPI NOR flash.
>
> The chip exposes valid JESD216B SFDP tables including 4-byte address
> instruction tables, from which geometry and opcodes are discovered.
> Stateless 4-byte opcodes and status register locking are enabled. Read,
> write, and erase functionality across the full memory array have been
> tested on hardware.
>
> Cc: stable@vger.kernel.org # v6.1+
> Co-developed-by: Adam Calabrigo <adamc@arista.com>
Co-developed-by for just adding an id?
Please note that we have some requirements for new flashes, see [1].
Same for the your other patch.
-michael
[1] https://docs.kernel.org/driver-api/mtd/spi-nor.html
> Signed-off-by: Adam Calabrigo <adamc@arista.com>
> Signed-off-by: Matthew Parker <mparker@arista.com>
> ---
> drivers/mtd/spi-nor/gigadevice.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/gigadevice.c b/drivers/mtd/spi-nor/gigadevice.c
> index 6a2e6ebda148..de96cefde516 100644
> --- a/drivers/mtd/spi-nor/gigadevice.c
> +++ b/drivers/mtd/spi-nor/gigadevice.c
> @@ -64,6 +64,10 @@ static const struct flash_info gigadevice_nor_parts[] = {
> .id = SNOR_ID(0xc8, 0x40, 0x19),
> .name = "gd25q256",
> .flags = SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB | SPI_NOR_TB_SR_BIT6,
> + }, {
> + .id = SNOR_ID(0xc8, 0x47, 0x1a),
> + .flags = SPI_NOR_HAS_LOCK,
> + .fixup_flags = SPI_NOR_4B_OPCODES,
> }, {
> .id = SNOR_ID(0xc8, 0x60, 0x16),
> .name = "gd25lq32",
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-11-09 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 2:20 [PATCH] mtd: spi-nor: gigadevice: Add support for GigaDevice GD25B512 Matthew Parker
2026-11-08 2:20 ` Matthew Parker
2026-11-08 2:28 ` sashiko-bot
2026-11-09 8:51 ` Michael Walle [this message]
2026-11-09 8:51 ` Michael Walle
-- strict thread matches above, loose matches on Subject: below --
2026-11-08 2:17 Matthew Parker
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=DMQJVVTSK5MO.2VQC80RTHL9LN@kernel.org \
--to=mwalle@kernel.org \
--cc=adamc@arista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mparker@arista.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.