From: Vladimir Oltean <olteanv@gmail.com>
To: WeiHao Li <cn.liweihao@gmail.com>
Cc: heiko@sntech.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] arm64: dts: rockchip: Add USB2.0 PHY for RK3368
Date: Thu, 12 Feb 2026 18:55:50 +0200 [thread overview]
Message-ID: <20260212165550.mju3377fvphdsqoe@skbuf> (raw)
In-Reply-To: <20250909132958.26423-3-cn.liweihao@gmail.com>
On Tue, Sep 09, 2025 at 09:29:56PM +0800, WeiHao Li wrote:
> RK3368 has one USB2.0 PHY with two ports, This adds device tree node for
> it.
>
> Signed-off-by: WeiHao Li <cn.liweihao@gmail.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3368.dtsi | 29 ++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3368.dtsi b/arch/arm64/boot/dts/rockchip/rk3368.dtsi
> index 1b21787269..b09e431a64 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3368.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3368.dtsi
> @@ -766,11 +766,40 @@ cru: clock-controller@ff760000 {
> grf: syscon@ff770000 {
> compatible = "rockchip,rk3368-grf", "syscon", "simple-mfd";
> reg = <0x0 0xff770000 0x0 0x1000>;
> + #address-cells = <1>;
> + #size-cells = <1>;
This introduces a device tree warning. You cannot mix nodes with no unit
address (io-domains) with nodes with a unit address (usb2-phy@700) on
the same hierarchical level. You have to pick a format and stick to it.
>
> io_domains: io-domains {
> compatible = "rockchip,rk3368-io-voltage-domain";
> status = "disabled";
> };
> +
> + u2phy: usb2-phy@700 {
> + compatible = "rockchip,rk3368-usb2phy";
> + reg = <0x700 0x2c>;
> + clocks = <&cru SCLK_OTGPHY0>;
> + clock-names = "phyclk";
> + clock-output-names = "usb480m_phy";
> + #clock-cells = <0>;
> + status = "disabled";
> +
> + u2phy_otg: otg-port {
> + interrupts = <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 93 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 95 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "otg-bvalid", "otg-id",
> + "linestate";
> + #phy-cells = <0>;
> + status = "disabled";
> + };
> +
> + u2phy_host: host-port {
> + interrupts = <GIC_SPI 96 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "linestate";
> + #phy-cells = <0>;
> + status = "disabled";
> + };
> + };
> };
>
> wdt: watchdog@ff800000 {
> --
> 2.47.2
>
>
next prev parent reply other threads:[~2026-02-12 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 13:29 [PATCH v2 0/4] Fix USB controller support for RK3368 WeiHao Li
2025-09-09 13:29 ` [PATCH v2 1/4] phy: rockchip: inno-usb2: Add usb2 phy " WeiHao Li
2025-09-11 8:53 ` Heiko Stübner
2026-02-21 14:59 ` Heiko Stübner
2025-09-09 13:29 ` [PATCH v2 2/4] arm64: dts: rockchip: Add USB2.0 PHY " WeiHao Li
2026-02-12 16:55 ` Vladimir Oltean [this message]
2026-02-18 22:52 ` Johan Jonker
2025-09-09 13:29 ` [PATCH v2 3/4] dt-bindings: phy: rockchip,inno-usb2phy: Document rk3368 usb phy WeiHao Li
2025-09-09 13:29 ` [PATCH v2 4/4] arm64: dts: rockchip: Add phys attribute of USB host node for RK3368 WeiHao Li
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=20260212165550.mju3377fvphdsqoe@skbuf \
--to=olteanv@gmail.com \
--cc=cn.liweihao@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--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