mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Takahiro.Kuwano@infineon.com>
To: <miquel.raynal@bootlin.com>, <mwalle@kernel.org>
Cc: <pratyush@kernel.org>, <richard@nod.at>, <vigneshr@ti.com>,
	<tudor.ambarus@linaro.org>, <linux-mtd@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [RFC PATCH 0/3] mtd: spi-nor: Rework flash parameter initialization
Date: Wed, 3 Jun 2026 00:13:58 +0000	[thread overview]
Message-ID: <c8f082b6deb4483b9a6a5f54ac549d62@infineon.com> (raw)
In-Reply-To: <87tsrlmf7g.fsf@bootlin.com>

Hi,

> Hi Michael,
> 
> On 01/06/2026 at 14:52:42 +02, Michael Walle <mwalle@kernel.org> wrote:
> 
> > Try to simplify the flash initialization and get rid of the legacy
> > handling. As default, all the flags of the in-kernel database are
> > taken and amended with the SFDP data.
> >
> > This might have the consequence that all the flashes now get a
> > RDSFPD opcode which might be an unknown opcode. But that was already
> > the case for any flashes which were unknown to the linux kernel. So
> > far, there was not a single complaint.
> >
> > See patch 3 for more information. If feedback is positive, this is
> > intended to be applied to the spi-nor tree after the next merge
> > window, so it will sit around in -next for quite some time and get
> > some testing.
> >
> > That being said, I've just did a quick test on my boards. Please
> > give it a test on your boards.
> 
> Interesting cleanup, thanks for pushing it. I'll run some tests with
> some old and newer SFDP based flashes. I do not have chips without SFDP
> though.
> 
I do have some non-SFDP chips (S25FL-S). Will get back to you with test
result.

Thanks,
Takahiro


  reply	other threads:[~2026-06-03  0:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 12:52 Michael Walle
2026-06-01 12:52 ` [RFC PATCH 1/3] mtd: spi-nor: spansion: s25fl256s0: remove SKIP_SFDP flag Michael Walle
2026-06-02  9:57   ` Miquel Raynal
2026-06-02 11:01     ` Michael Walle
2026-06-05  8:05   ` Takahiro.Kuwano
2026-06-05 13:05   ` Tudor Ambarus
2026-06-01 12:52 ` [RFC PATCH 2/3] mtd: spi-nor: don't clear the SNOR_F_4B_OPCODES flag on failure Michael Walle
2026-06-02  9:58   ` Miquel Raynal
2026-06-05  8:15   ` Takahiro.Kuwano
2026-06-05 13:05   ` Tudor Ambarus
2026-06-01 12:52 ` [RFC PATCH 3/3] mtd: spi-nor: rework flash parameter initialization Michael Walle
2026-06-05 13:17   ` Tudor Ambarus
2026-06-02 10:03 ` [RFC PATCH 0/3] mtd: spi-nor: Rework " Miquel Raynal
2026-06-03  0:13   ` Takahiro.Kuwano [this message]
2026-06-05  8:50     ` Takahiro.Kuwano
2026-07-02  2:39 ` Cheng Ming Lin
2026-07-02 15:17 ` Miquel Raynal
2026-07-07  6:35   ` Michael Walle
2026-07-06  6:24 ` Miquel Raynal
2026-07-06  7:33   ` Michael Walle
2026-07-06 13:45     ` Miquel Raynal
2026-07-06 14:16       ` Miquel Raynal

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=c8f082b6deb4483b9a6a5f54ac549d62@infineon.com \
    --to=takahiro.kuwano@infineon.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