From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Marek Vasut <marex@denx.de>, <linux-arm-kernel@lists.infradead.org>
Cc: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh@kernel.org>, <devicetree@vger.kernel.org>,
<kernel@dh-electronics.com>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH] ARM: dts: stm32: Add support for STM32MP13xx DHCOR SoM and DHSBC rev.200 board
Date: Mon, 10 Mar 2025 14:27:43 +0100 [thread overview]
Message-ID: <6d42bdc8-825a-4fd9-80ab-cfe02fff6c86@foss.st.com> (raw)
In-Reply-To: <20250302152605.54792-1-marex@denx.de>
Hi Marek
On 3/2/25 16:25, Marek Vasut wrote:
> LDO2 is expansion connector supply on STM32MP13xx DHCOR DHSBC rev.200.
> LDO5 is carrier board supply on STM32MP13xx DHCOR DHSBC rev.200. Keep
> both regulators always enabled to make sure both the carrier board and
> the expansion connector is always powered on and supplied with correct
> voltage.
>
> Describe ST33TPHF2XSPI TPM 2.0 chip interrupt and reset lines.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Cc: Christoph Niedermaier <cniedermaier@dh-electronics.com>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
> Cc: Rob Herring <robh@kernel.org>
> Cc: devicetree@vger.kernel.org
> Cc: kernel@dh-electronics.com
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-stm32@st-md-mailman.stormreply.com
> ---
> .../boot/dts/st/stm32mp135f-dhcor-dhsbc.dts | 30 +++++++++++++++++--
> 1 file changed, 28 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dts b/arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dts
> index 853dc21449d99..9902849ed0406 100644
> --- a/arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dts
> +++ b/arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dts
Applied on stm32-next.
Thanks
Alex
> @@ -176,7 +176,7 @@ &gpioa {
> gpio-line-names = "", "", "", "",
> "", "DHSBC_USB_PWR_CC1", "", "",
> "", "", "", "DHSBC_nETH1_RST",
> - "", "DHCOR_HW-CODING_0", "", "";
> + "", "DHCOR_HW-CODING_0", "", "DHSBC_HW-CODE_2";
> };
>
> &gpiob {
> @@ -197,7 +197,7 @@ &gpiod {
> gpio-line-names = "", "", "", "",
> "", "DHCOR_RAM-CODING_0", "", "",
> "", "DHCOR_RAM-CODING_1", "", "",
> - "", "", "", "";
> + "", "DHSBC_HW-CODE_1", "", "";
> };
>
> &gpioe {
> @@ -221,6 +221,13 @@ &gpiog {
> "DHSBC_ETH1_INTB", "", "", "DHSBC_ETH2_INTB";
> };
>
> +&gpioh {
> + gpio-line-names = "", "", "", "DHSBC_HW-CODE_0",
> + "", "", "", "",
> + "", "", "", "",
> + "", "", "", "";
> +};
> +
> &gpioi {
> gpio-line-names = "DHCOR_RTC_nINT", "DHCOR_HW-CODING_1",
> "DHCOR_BT_REG_ON", "DHCOR_PMIC_nINT",
> @@ -296,6 +303,9 @@ &spi2 {
> st33htph: tpm@0 {
> compatible = "st,st33htpm-spi", "tcg,tpm_tis-spi";
> reg = <0>;
> + interrupt-parent = <&gpioe>;
> + interrupts = <9 IRQ_TYPE_LEVEL_LOW>;
> + reset-gpios = <&gpioe 12 GPIO_ACTIVE_LOW>;
> spi-max-frequency = <24000000>;
> };
> };
> @@ -419,3 +429,19 @@ connector {
> type = "micro";
> };
> };
> +
> +/* LDO2 is expansion connector 3V3 supply on STM32MP13xx DHCOR DHSBC rev.200 */
> +&vdd_ldo2 {
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> +};
> +
> +/* LDO5 is carrier board 3V3 supply on STM32MP13xx DHCOR DHSBC rev.200 */
> +&vdd_sd {
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> +};
prev parent reply other threads:[~2025-03-10 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 15:25 [PATCH] ARM: dts: stm32: Add support for STM32MP13xx DHCOR SoM and DHSBC rev.200 board Marek Vasut
2025-03-10 13:27 ` Alexandre TORGUE [this message]
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=6d42bdc8-825a-4fd9-80ab-cfe02fff6c86@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=cniedermaier@dh-electronics.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@dh-electronics.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--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;
as well as URLs for NNTP newsgroup(s).