From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: Mateusz Nowicki <mateusz.nowicki@posteo.net>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: st: mark main supplies always-on on stm32mp257f-dk
Date: Wed, 7 Oct 2026 11:22:13 +0200 [thread overview]
Message-ID: <aaedc962-63ab-431b-8b27-b4ac9c11d16e@foss.st.com> (raw)
In-Reply-To: <20261004112421.47158-1-mateusz.nowicki@posteo.net>
Hi,
On 10/4/26 13:24, Mateusz Nowicki wrote:
> The vddcore, v1v8 and v3v3 regulators have no consumer in Linux, so
> the regulator core disables them 30 seconds after boot. They supply
> the SoC digital logic, the SoC 1.8 V analog domain and the 3.3 V board
> peripherals, and must stay on while Linux runs.
>
> Mark them always-on.
>
> Signed-off-by: Mateusz Nowicki <mateusz.nowicki@posteo.net>
> ---
> arch/arm64/boot/dts/st/stm32mp257f-dk.dts | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/st/stm32mp257f-dk.dts b/arch/arm64/boot/dts/st/stm32mp257f-dk.dts
> index a8f18508db3e..7a837e6fd578 100644
> --- a/arch/arm64/boot/dts/st/stm32mp257f-dk.dts
> +++ b/arch/arm64/boot/dts/st/stm32mp257f-dk.dts
> @@ -310,14 +310,17 @@ scmi_vddio1: regulator@0 {
> scmi_vddcore: regulator@11 {
> reg = <VOLTD_SCMI_STPMIC2_BUCK2>;
> regulator-name = "vddcore";
> + regulator-always-on;
> };
> scmi_v1v8: regulator@14 {
> reg = <VOLTD_SCMI_STPMIC2_BUCK5>;
> regulator-name = "v1v8";
> + regulator-always-on;
> };
> scmi_v3v3: regulator@16 {
> reg = <VOLTD_SCMI_STPMIC2_BUCK7>;
> regulator-name = "v3v3";
> + regulator-always-on;
> };
> scmi_vdd_emmc: regulator@18 {
> reg = <VOLTD_SCMI_STPMIC2_LDO2>;
>
> base-commit: f831584128ac2a36fb4fa62fe106793d08c2dbf1
For STMicroelectronics boards, the STPMIC always-on regulator are
managed on SCMI server side in OP-TEE.
So no need to manage this constraint in Linux device tree.
This always-on regulator are exposed only for information or to be used
are supply for some IP.
Regards
Patrick
next prev parent reply other threads:[~2026-10-07 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 11:24 Mateusz Nowicki
2026-10-07 9:22 ` Patrick DELAUNAY [this message]
2026-10-08 11:43 ` mateusz.nowicki
2026-10-09 8:17 ` Patrick DELAUNAY
2026-10-09 9:29 ` mateusz.nowicki
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=aaedc962-63ab-431b-8b27-b4ac9c11d16e@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mateusz.nowicki@posteo.net \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®