From: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
To: <alexandre.torgue@foss.st.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: <amelie.delaunay@foss.st.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<fabrice.gasnier@foss.st.com>
Subject: [PATCH v2 02/10] ARM: dts: stm32: add USBPHYC and dual USB HS PHY support on stm32mp131
Date: Fri, 14 Oct 2022 16:15:01 +0200 [thread overview]
Message-ID: <20221014141509.211149-3-fabrice.gasnier@foss.st.com> (raw)
In-Reply-To: <20221014141509.211149-1-fabrice.gasnier@foss.st.com>
From: Amelie Delaunay <amelie.delaunay@foss.st.com>
This patch adds support for USBPHYC and its two USB HS PHY on stm32mp131.
Signed-off-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
---
arch/arm/boot/dts/stm32mp131.dtsi | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp131.dtsi b/arch/arm/boot/dts/stm32mp131.dtsi
index e0e0e27a9221..cd31fdd47536 100644
--- a/arch/arm/boot/dts/stm32mp131.dtsi
+++ b/arch/arm/boot/dts/stm32mp131.dtsi
@@ -409,6 +409,29 @@ iwdg2: watchdog@5a002000 {
status = "disabled";
};
+ usbphyc: usbphyc@5a006000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ #clock-cells = <0>;
+ compatible = "st,stm32mp1-usbphyc";
+ reg = <0x5a006000 0x1000>;
+ clocks = <&rcc USBPHY_K>;
+ resets = <&rcc USBPHY_R>;
+ vdda1v1-supply = <®11>;
+ vdda1v8-supply = <®18>;
+ status = "disabled";
+
+ usbphyc_port0: usb-phy@0 {
+ #phy-cells = <0>;
+ reg = <0>;
+ };
+
+ usbphyc_port1: usb-phy@1 {
+ #phy-cells = <1>;
+ reg = <1>;
+ };
+ };
+
rtc: rtc@5c004000 {
compatible = "st,stm32mp1-rtc";
reg = <0x5c004000 0x400>;
--
2.25.1
next prev parent reply other threads:[~2022-10-14 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 14:14 [PATCH v2 00/10] Add support for USB on STM32MP13 Fabrice Gasnier
2022-10-14 14:15 ` [PATCH v2 01/10] ARM: dts: stm32: add PWR fixed regulators on stm32mp131 Fabrice Gasnier
2022-10-14 14:15 ` Fabrice Gasnier [this message]
2022-10-14 14:15 ` [PATCH v2 03/10] ARM: dts: stm32: add UBSH EHCI and OHCI support " Fabrice Gasnier
2022-10-14 14:15 ` [PATCH v2 04/10] ARM: dts: stm32: add USB OTG HS " Fabrice Gasnier
2022-10-14 14:15 ` [PATCH v2 05/10] ARM: dts: stm32: add fixed regulators to support usb on stm32mp135f-dk Fabrice Gasnier
2022-10-14 14:15 ` [PATCH v2 06/10] ARM: dts: stm32: enable USB HS phys " Fabrice Gasnier
2022-10-14 14:15 ` [PATCH v2 07/10] ARM: dts: stm32: enable USB Host EHCI " Fabrice Gasnier
2022-10-14 14:15 ` [PATCH v2 08/10] ARM: dts: stm32: add pins for stm32g0 typec controller on stm32mp13 Fabrice Gasnier
2022-10-14 14:15 ` [PATCH v2 09/10] ARM: dts: stm32: enable USB OTG in dual role mode on stm32mp135f-dk Fabrice Gasnier
2022-10-14 14:15 ` [PATCH v2 10/10] ARM: multi_v7_defconfig: enable Type-C UCSI and STM32G0 as modules Fabrice Gasnier
2022-10-24 10:01 ` [PATCH v2 00/10] Add support for USB on STM32MP13 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=20221014141509.211149-3-fabrice.gasnier@foss.st.com \
--to=fabrice.gasnier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.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).