From: Hrushikesh Salunke <h-salunke@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <s-vadapalli@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<h-salunke@ti.com>, <danishanwar@ti.com>
Subject: [PATCH v2 3/4] arm64: dts: ti: k3-am62x-sk-common: Add bootph-all tag to usb0_phy_ctrl node
Date: Tue, 2 Sep 2025 11:00:08 +0530 [thread overview]
Message-ID: <20250902053009.1732607-4-h-salunke@ti.com> (raw)
In-Reply-To: <20250902053009.1732607-1-h-salunke@ti.com>
Add bootph-all property to the USB0 PHY controller node to make it
available during all boot phases. This is required for USB DFU boot.
Signed-off-by: Hrushikesh Salunke <h-salunke@ti.com>
---
arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi b/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
index 13e1d36123d5..554def7b5c55 100644
--- a/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
@@ -530,6 +530,10 @@ usb0_hs_ep: endpoint {
};
};
+&usb0_phy_ctrl {
+ bootph-all;
+};
+
&usb1 {
dr_mode = "host";
pinctrl-names = "default";
--
2.34.1
next prev parent reply other threads:[~2025-09-02 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 5:30 [PATCH v2 0/4] arm64: dts: ti: Add bootph-all tag to USB PHY controller Hrushikesh Salunke
2025-09-02 5:30 ` [PATCH v2 1/4] arm64: dts: ti: k3-am62a7-sk: Add bootph-all tag to usb0_phy_ctrl node Hrushikesh Salunke
2025-09-02 5:30 ` [PATCH v2 2/4] arm64: dts: ti: k3-am62p5-sk: " Hrushikesh Salunke
2025-09-02 5:30 ` Hrushikesh Salunke [this message]
2025-09-02 5:30 ` [PATCH v2 4/4] arm64: dts: ti: k3-j722s-evm: " Hrushikesh Salunke
2025-09-03 9:52 ` [PATCH v2 0/4] arm64: dts: ti: Add bootph-all tag to USB PHY controller s-vadapalli
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=20250902053009.1732607-4-h-salunke@ti.com \
--to=h-salunke@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.com \
/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).