From: Sean Nyekjaer <sean@geanix.com>
To: l.goehrs@pengutronix.de, a.fatoum@pengutronix.de,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Sean Nyekjaer <sean@geanix.com>,
dantuguf14105@gmail.com, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 5/9] ARM: dts: stm32: osd32: fix ldo2 not required to be always-on
Date: Wed, 12 Jul 2023 14:42:43 +0200 [thread overview]
Message-ID: <20230712124248.2400862-5-sean@geanix.com> (raw)
In-Reply-To: <20230712124248.2400862-1-sean@geanix.com>
According to the OSD32MP1 Power System overview[1] there is no hard
requirement for the ldo2 to be always-on.
[1]: https://octavosystems.com/app_notes/osd32mp1-power-system-overview/#connections
Signed-off-by: Sean Nyekjaer <sean@geanix.com>
Acked-by: Leonard Göhrs <l.goehrs@pengutronix.de>
---
arch/arm/boot/dts/st/stm32mp15xx-osd32.dtsi | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/boot/dts/st/stm32mp15xx-osd32.dtsi b/arch/arm/boot/dts/st/stm32mp15xx-osd32.dtsi
index eb43a1e3a0c9..902ca6c23533 100644
--- a/arch/arm/boot/dts/st/stm32mp15xx-osd32.dtsi
+++ b/arch/arm/boot/dts/st/stm32mp15xx-osd32.dtsi
@@ -124,9 +124,7 @@ v3v3_hdmi: ldo2 {
regulator-name = "v3v3_hdmi";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
- regulator-always-on;
interrupts = <IT_CURLIM_LDO2 0>;
-
};
vtt_ddr: ldo3 {
--
2.40.0
next prev parent reply other threads:[~2023-07-12 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 12:42 [PATCH v4 1/9] ARM: dts: stm32: Add alternate pinmux for i2s pins Sean Nyekjaer
2023-07-12 12:42 ` [PATCH v4 2/9] ARM: dts: stm32: Add alternate pinmux for ldtc pins Sean Nyekjaer
2023-07-12 12:42 ` [PATCH v4 3/9] ARM: dts: stm32: Add alternate pinmux for can pins Sean Nyekjaer
2023-07-12 12:42 ` [PATCH v4 4/9] ARM: dts: stm32: osd32: fix ldo1 not required to be always-on Sean Nyekjaer
2023-07-12 12:42 ` Sean Nyekjaer [this message]
2023-07-12 12:42 ` [PATCH v4 6/9] ARM: dts: stm32: lxa-tac: remove v3v3_hdmi override Sean Nyekjaer
2023-07-12 12:42 ` [PATCH v4 7/9] ARM: dts: stm32: osd32: fix ldo6 not required to be always-on Sean Nyekjaer
2023-07-12 12:42 ` [PATCH v4 8/9] dt-bindings: arm: stm32: add extra SiP compatible for oct,stm32mp157c-osd32-red Sean Nyekjaer
2023-07-12 18:10 ` Conor Dooley
2023-07-12 19:29 ` Krzysztof Kozlowski
2023-07-12 12:42 ` [PATCH v4 9/9] ARM: dts: stm32: Add Octavo OSD32MP1-RED board Sean Nyekjaer
2023-08-10 11:37 ` Alexandre TORGUE
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=20230712124248.2400862-5-sean@geanix.com \
--to=sean@geanix.com \
--cc=a.fatoum@pengutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=dantuguf14105@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.goehrs@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).