From: Tom Rini <trini@konsulko.com>
To: Michael Walle <mwalle@kernel.org>
Cc: Conor Dooley <conor@kernel.org>,
u-boot@lists.denx.de, Tudor Ambarus <tudor.ambarus@linaro.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Takahiro Kuwano <Takahiro.Kuwano@infineon.com>,
Hiroyuki Saito <Hiroyuki.Saito2@infineon.com>,
Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>,
Prasanth Babu Mantena <p-mantena@ti.com>,
Vaishnav Achath <vaishnav.a@ti.com>,
Prasad Kummari <prasad.kummari@amd.com>
Subject: Re: [RFH] SPI and SPI-NOR patch help
Date: Mon, 16 Feb 2026 09:31:10 -0600 [thread overview]
Message-ID: <20260216153110.GV2747538@bill-the-cat> (raw)
In-Reply-To: <DGG8OA1O1UEL.12RR559TX4XX6@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]
On Mon, Feb 16, 2026 at 09:21:55AM +0100, Michael Walle wrote:
> On Sat Feb 14, 2026 at 7:58 PM CET, Conor Dooley wrote:
> > On Fri, Feb 13, 2026 at 10:46:07AM -0600, Tom Rini wrote:
> >> Hey all,
> >>
> >> To be blunt, U-Boot needs help with reviewing and maintaining the SPI
> >> and SPI-NOR subsystems. We haven't had someone with time to actively
> >> work in this area for some time. I'm going through the outstanding
> >> changes now, but it also seems a common problem is that with respect to
> >> device IDs, most of the new ones also aren't in the upstream Linux
> >> Kernel. Is there some better and generic solution we're missing so that
> >> we don't have large and often growing device ID tables? I'd rather not
> >> make that problem worse, so I've rejected two of those types of updates
> >> today and I'm just setting aside a large number of others.
> >
> > Dunno if your timing was cursed on sending this, but Tudor submitted his
> > resignation from spi-nor maintainership in the kernel about 10 mins
> > after.
> > I think Michael Walle might be responsible for what you're talking about
> > here, with his 773bbe1044973 ("mtd: spi-nor: add generic flash driver"),
> > but idk jack about spi-nor stuff.
>
> Yeah. Nowadays SPI-NOR flashes come with self describing tables,
> which are already supported by u-boot, I think. The only change that
> seems to be missing is the fallback to it if an id isn't found in
> the flashdb. Only thing is, the SFDP doesn't describe all features,
> most prominent example being locking. So if you need that, you'll
> still need to have an entry per flash.
>
> In fact, in linux I'm planning to change to make it probe SFDP first
> and then amend it with the flashdb information (if there is an
> entry).
Thanks for explaining. So in that U-Boot does have SFDP support, the
first thing is platforms should likely be enabling that instead of just
adding IDs, at least for basic support. It still leaves us in a bad spot
about having SPI and SPI-NOR stuff reviewed and maintained, but at least
it's clearer in public now where it stands.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-16 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 16:46 [RFH] SPI and SPI-NOR patch help Tom Rini
2026-02-14 18:58 ` Conor Dooley
2026-02-16 8:21 ` Michael Walle
2026-02-16 15:31 ` Tom Rini [this message]
2026-02-18 9:23 ` Miquel Raynal
2026-02-18 14:20 ` Peter Robinson
2026-02-19 10:26 ` Miquel Raynal
2026-02-19 12:13 ` Tudor Ambarus
2026-02-19 20:57 ` Tom Rini
2026-02-20 7:35 ` Tudor Ambarus
2026-02-20 15:07 ` Tom Rini
2026-02-24 8:39 ` Takahiro.Kuwano
2026-02-24 10:23 ` Tudor Ambarus
2026-02-24 15:40 ` Tom Rini
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=20260216153110.GV2747538@bill-the-cat \
--to=trini@konsulko.com \
--cc=Hiroyuki.Saito2@infineon.com \
--cc=Takahiro.Kuwano@infineon.com \
--cc=conor@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=p-mantena@ti.com \
--cc=prasad.kummari@amd.com \
--cc=tudor.ambarus@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=vaishnav.a@ti.com \
--cc=venkatesh.abbarapu@amd.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