Re: [RFC PATCH 0/3] mtd: spi-nor: Rework flash parameter initialization

From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Michael Walle <mwalle@kernel.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	 Takahiro Kuwano <takahiro.kuwano@infineon.com>,
	 Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	 Tudor Ambarus <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: Tue, 02 Jun 2026 12:03:47 +0200	[thread overview]
Message-ID: <87tsrlmf7g.fsf@bootlin.com> (raw)
In-Reply-To: <20260601125438.3481722-1-mwalle@kernel.org> (Michael Walle's message of "Mon, 1 Jun 2026 14:52:42 +0200")

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.

Thanks,
Miquèl