From: Vishwaroop A <va@nvidia.com>
To: <tudor.ambarus@linaro.org>, <pratyush@kernel.org>,
<mwalle@kernel.org>, <cmiquel.raynal@bootlin.com>,
<thierry.reding@gmail.com>, <richard@nod.at>, <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<jonathanh@nvidia.com>, <kyarlagadda@nvidia.com>,
<smangipudi@nvidia.com>
Cc: Vishwaroop A <va@nvidia.com>
Subject: [PATCH 0/3] Add support for S25FS512S1, and MX25U51279G
Date: Tue, 26 Nov 2024 18:58:31 +0000 [thread overview]
Message-ID: <20241126185834.1130949-1-va@nvidia.com> (raw)
This patch series adds support for three 64MB SPI NOR flash devices:
1. S25FS512S: Add a post-get-map-id fixup to address an issue with
the SFDP Address Map incorrectly reporting map ID as 0.
2. S25FS512S1: Add support for this Spansion device, including
dual/quad read capabilities and s25fs_s_nor_fixups.
3. MX25U51279G: Add support for this Macronix device with 4K sector
erase, dual/quad read capabilities, and 4-byte opcode support.
Vishwaroop A (3):
mtd: spi-nor: Add post-get-map-id fixup for S25FS512S/S1
mtd: spi-nor: Add support for spansion s25fs512s1
mtd: spi-nor: Add support for mx25u51279g
drivers/mtd/spi-nor/core.c | 25 ++++++++++++++++++
drivers/mtd/spi-nor/core.h | 4 +++
drivers/mtd/spi-nor/macronix.c | 6 +++++
drivers/mtd/spi-nor/sfdp.c | 7 +++++
drivers/mtd/spi-nor/spansion.c | 48 ++++++++++++++++++++++++++++++++++
5 files changed, 90 insertions(+)
--
2.17.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Vishwaroop A <va@nvidia.com>
To: <tudor.ambarus@linaro.org>, <pratyush@kernel.org>,
<mwalle@kernel.org>, <cmiquel.raynal@bootlin.com>,
<thierry.reding@gmail.com>, <richard@nod.at>, <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<jonathanh@nvidia.com>, <kyarlagadda@nvidia.com>,
<smangipudi@nvidia.com>
Cc: Vishwaroop A <va@nvidia.com>
Subject: [PATCH 0/3] Add support for S25FS512S1, and MX25U51279G
Date: Tue, 26 Nov 2024 18:58:31 +0000 [thread overview]
Message-ID: <20241126185834.1130949-1-va@nvidia.com> (raw)
This patch series adds support for three 64MB SPI NOR flash devices:
1. S25FS512S: Add a post-get-map-id fixup to address an issue with
the SFDP Address Map incorrectly reporting map ID as 0.
2. S25FS512S1: Add support for this Spansion device, including
dual/quad read capabilities and s25fs_s_nor_fixups.
3. MX25U51279G: Add support for this Macronix device with 4K sector
erase, dual/quad read capabilities, and 4-byte opcode support.
Vishwaroop A (3):
mtd: spi-nor: Add post-get-map-id fixup for S25FS512S/S1
mtd: spi-nor: Add support for spansion s25fs512s1
mtd: spi-nor: Add support for mx25u51279g
drivers/mtd/spi-nor/core.c | 25 ++++++++++++++++++
drivers/mtd/spi-nor/core.h | 4 +++
drivers/mtd/spi-nor/macronix.c | 6 +++++
drivers/mtd/spi-nor/sfdp.c | 7 +++++
drivers/mtd/spi-nor/spansion.c | 48 ++++++++++++++++++++++++++++++++++
5 files changed, 90 insertions(+)
--
2.17.1
next reply other threads:[~2024-11-26 18:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 18:58 Vishwaroop A [this message]
2024-11-26 18:58 ` [PATCH 0/3] Add support for S25FS512S1, and MX25U51279G Vishwaroop A
2024-11-26 18:58 ` [PATCH 1/3] mtd: spi-nor: Add post-get-map-id fixup for S25FS512S/S1 Vishwaroop A
2024-11-26 18:58 ` Vishwaroop A
2024-12-06 15:05 ` Pratyush Yadav
2024-12-06 15:05 ` Pratyush Yadav
2024-11-26 18:58 ` [PATCH 2/3] mtd: spi-nor: Add support for spansion s25fs512s1 Vishwaroop A
2024-11-26 18:58 ` Vishwaroop A
2024-12-06 15:08 ` Pratyush Yadav
2024-12-06 15:08 ` Pratyush Yadav
2024-11-26 18:58 ` [PATCH 3/3] mtd: spi-nor: Add support for mx25u51279g Vishwaroop A
2024-11-26 18:58 ` Vishwaroop A
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=20241126185834.1130949-1-va@nvidia.com \
--to=va@nvidia.com \
--cc=cmiquel.raynal@bootlin.com \
--cc=jonathanh@nvidia.com \
--cc=kyarlagadda@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@gmail.com \
--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 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.