From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Cc: 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: [RFH] SPI and SPI-NOR patch help
Date: Fri, 13 Feb 2026 10:46:07 -0600 [thread overview]
Message-ID: <20260213164607.GI2747538@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
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.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2026-02-13 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 16:46 Tom Rini [this message]
2026-02-14 18:58 ` [RFH] SPI and SPI-NOR patch help Conor Dooley
2026-02-16 8:21 ` Michael Walle
2026-02-16 15:31 ` Tom Rini
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=20260213164607.GI2747538@bill-the-cat \
--to=trini@konsulko.com \
--cc=Hiroyuki.Saito2@infineon.com \
--cc=Takahiro.Kuwano@infineon.com \
--cc=miquel.raynal@bootlin.com \
--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