From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Cc: Manoj Sai <abbaraju.manojsai@amarulasolutions.com>,
Matteo Lisi <matteo.lisi@engicam.com>,
Teresa Remmet <t.remmet@phytec.de>, Peng Fan <peng.fan@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Marco Franchi <marcofrk@gmail.com>,
Alifer Moraes <alifer.wsdm@gmail.com>,
"Lukas F. Hartmann" <lukas@mntre.com>,
Patrick Wildt <patrick@blueri.se>,
Heiko Thiery <heiko.thiery@gmail.com>,
Marek Vasut <marex@denx.de>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
upstream@lists.phytec.de
Subject: U-Boot and legacy SPL power control on modern platforms
Date: Fri, 20 Mar 2026 15:45:18 -0600 [thread overview]
Message-ID: <20260320214518.GD502704@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
Hello,
As part of the work I've been doing on clarifying Kconfig dependencies
I've stumbled on to a number of modern boards[1] that are using the
SPL_POWER_LEGACY symbol. Can the maintainers please update these to use
DM_PMIC, DM_REGULATOR (and SPL variants) as needed so that they use the
modern architecture, or let me know what's missing here? Thanks!
--
Tom
[1]: imx8mp-icore-mx8mp-edimm2.2 imx8mp-libra-fpsc imx8mq_evk
imx8mq_phanbell imx8mq_reform2 kontron_pitx_imx8m phycore-imx8mp
pico-imx8mq verdin-imx8mp
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2026-03-20 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 21:45 Tom Rini [this message]
2026-03-22 12:26 ` U-Boot and legacy SPL power control on modern platforms Peng Fan (OSS)
2026-03-24 9:18 ` Francesco Dolcini
2026-03-25 11:18 ` Peng Fan
2026-03-25 16:52 ` Tom Rini
2026-03-25 17:56 ` Simon Glass
2026-03-26 7:44 ` Peng Fan
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=20260320214518.GD502704@bill-the-cat \
--to=trini@konsulko.com \
--cc=abbaraju.manojsai@amarulasolutions.com \
--cc=alifer.wsdm@gmail.com \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=heiko.thiery@gmail.com \
--cc=lukas@mntre.com \
--cc=marcofrk@gmail.com \
--cc=marex@denx.de \
--cc=matteo.lisi@engicam.com \
--cc=patrick@blueri.se \
--cc=peng.fan@nxp.com \
--cc=t.remmet@phytec.de \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.