From: Flaviu Nistor <flaviu.nistor@gmail.com>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
Michael Walle <mwalle@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
flaviu.nistor@gmail.com
Subject: Re: [PATCH] mtd: spi-nor: issi: Add support for is25wx01g
Date: Tue, 2 Sep 2025 21:38:18 +0300 [thread overview]
Message-ID: <20250902183818.17415-1-flaviu.nistor@gmail.com> (raw)
In-Reply-To: <mafs0cy8aw0yf.fsf@kernel.org>
> Hi Flaviu,
>
> On Mon, Sep 01 2025, Flaviu Nistor wrote:
>
>> Add support for the IS25WX01G 128MB (1Gb) ISSI Serial Flash Memory.
>>
>> Signed-off-by: Flaviu Nistor <flaviu.nistor@gmail.com>
>> ---
>> drivers/mtd/spi-nor/issi.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/mtd/spi-nor/issi.c b/drivers/mtd/spi-nor/issi.c
>> index 18d9a00aa22e..e4997f9bd557 100644
>> --- a/drivers/mtd/spi-nor/issi.c
>> +++ b/drivers/mtd/spi-nor/issi.c
>> @@ -126,6 +126,9 @@ static const struct flash_info issi_nor_parts[] = {
>> .flags = SPI_NOR_QUAD_PP,
>> .fixups = &is25lp256_fixups,
>> .fixup_flags = SPI_NOR_4B_OPCODES,
>> + }, {
>> + /* IS25WX01G */
>> + .id = SNOR_ID(0x9d, 0x5b, 0x1b),
>
> It seems the flash needs no special configuration. IIUC it can be driven
> entirely based on SFDP data. In that case, I don't think there is a need
> for an entry at all. The generic SFDP-based driver should already be
> enough for your flash. Just add a "jedec,spi-nor" node to your DT and it
> should work.
Thanks for the review and the explanation. I now see in
the core driver that spi_nor_check_sfdp_signature() is
used if spi_nor_match_id() does not find a valid entry.
>
>> }
>> };
prev parent reply other threads:[~2025-09-02 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 16:42 Flaviu Nistor
2025-09-01 17:13 ` Pratyush Yadav
2025-09-02 18:38 ` Flaviu Nistor [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=20250902183818.17415-1-flaviu.nistor@gmail.com \
--to=flaviu.nistor@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®