From: Francesco Dolcini <francesco@dolcini.it>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Tom Rini <trini@konsulko.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
Manoj Sai <abbaraju.manojsai@amarulasolutions.com>,
"matteo.lisi" <matteo.lisi@engicam.com>,
Teresa Remmet <T.remmet@phytec.de>,
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" <upstream@lists.phytec.de>
Subject: Re: U-Boot and legacy SPL power control on modern platforms
Date: Tue, 24 Mar 2026 10:18:58 +0100 [thread overview]
Message-ID: <20260324091858.GA22537@francesco-nb> (raw)
In-Reply-To: <PAXPR04MB84595AE69ADF07A9F9FAB7B1884AA@PAXPR04MB8459.eurprd04.prod.outlook.com>
On Sun, Mar 22, 2026 at 12:26:46PM +0000, Peng Fan (OSS) wrote:
> > 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!
>
> If board maintainers would work on the migration, that would be great.
> If not, I will give a check, but I not have the board to test.
Thanks Peng, I have seen the patch on Verdin and I'll test/review the code.
Francesco
next prev parent reply other threads:[~2026-03-24 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 21:45 U-Boot and legacy SPL power control on modern platforms Tom Rini
2026-03-22 12:26 ` Peng Fan (OSS)
2026-03-24 9:18 ` Francesco Dolcini [this message]
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=20260324091858.GA22537@francesco-nb \
--to=francesco@dolcini.it \
--cc=T.remmet@phytec.de \
--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@oss.nxp.com \
--cc=trini@konsulko.com \
--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.