From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: jonas@kwiboo.se, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Chukun Pan <amadeus@jmu.edu.cn>
Subject: Re: [PATCH v2 4/5] arm64: dts: rockchip: Enable USB 2.0 ports on ArmSoM Sige1
Date: Fri, 29 May 2026 00:12:33 +0200 [thread overview]
Message-ID: <6849370.F8r316W7xa@phil> (raw)
In-Reply-To: <20260525070010.1060602-1-amadeus@jmu.edu.cn>
Am Montag, 25. Mai 2026, 09:00:10 Mitteleuropäische Sommerzeit schrieb Chukun Pan:
> Hi,
>
> > +&usb_host0_xhci {
> > + extcon = <&usb2phy>;
> > + maximum-speed = "high-speed";
> > + phys = <&usb2phy_otg>;
> > + phy-names = "usb2-phy";
>
> The same warning for this otg port:
> [ 0.232211] dwc3 fe500000.usb: Configuration mismatch. dr_mode forced to host
According to the schematics, this is an actual Type-C port, so not really
sure what the controller or driver is doing there.
Could you possibly check which condition in
dwc3_get_dr_mode() in drivers/usb/dwc3/core.c is triggering this?
> > +&usb2phy_otg {
> > + status = "okay";
> > +};
>
> OTG port missing: `vbus-supply = <&vcc5v0_usb_otg>;` [1]
I've added the supply now.
Thanks for testing
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: jonas@kwiboo.se, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Chukun Pan <amadeus@jmu.edu.cn>
Subject: Re: [PATCH v2 4/5] arm64: dts: rockchip: Enable USB 2.0 ports on ArmSoM Sige1
Date: Fri, 29 May 2026 00:12:33 +0200 [thread overview]
Message-ID: <6849370.F8r316W7xa@phil> (raw)
In-Reply-To: <20260525070010.1060602-1-amadeus@jmu.edu.cn>
Am Montag, 25. Mai 2026, 09:00:10 Mitteleuropäische Sommerzeit schrieb Chukun Pan:
> Hi,
>
> > +&usb_host0_xhci {
> > + extcon = <&usb2phy>;
> > + maximum-speed = "high-speed";
> > + phys = <&usb2phy_otg>;
> > + phy-names = "usb2-phy";
>
> The same warning for this otg port:
> [ 0.232211] dwc3 fe500000.usb: Configuration mismatch. dr_mode forced to host
According to the schematics, this is an actual Type-C port, so not really
sure what the controller or driver is doing there.
Could you possibly check which condition in
dwc3_get_dr_mode() in drivers/usb/dwc3/core.c is triggering this?
> > +&usb2phy_otg {
> > + status = "okay";
> > +};
>
> OTG port missing: `vbus-supply = <&vcc5v0_usb_otg>;` [1]
I've added the supply now.
Thanks for testing
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-05-28 22:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 17:12 [PATCH v2 0/5] rockchip: add USB nodes for RK3528 Heiko Stuebner
2026-05-05 17:12 ` Heiko Stuebner
2026-05-05 17:12 ` [PATCH v2 1/5] arm64: dts: rockchip: Add " Heiko Stuebner
2026-05-05 17:12 ` Heiko Stuebner
2026-05-05 17:12 ` [PATCH v2 2/5] arm64: dts: rockchip: Enable USB 2.0 ports on Radxa E20C Heiko Stuebner
2026-05-05 17:12 ` Heiko Stuebner
2026-05-25 6:50 ` Chukun Pan
2026-05-25 6:50 ` Chukun Pan
2026-05-28 5:57 ` Heiko Stuebner
2026-05-28 5:57 ` Heiko Stuebner
2026-05-29 7:00 ` Chukun Pan
2026-05-29 7:00 ` Chukun Pan
2026-05-05 17:12 ` [PATCH v2 3/5] arm64: dts: rockchip: Enable USB ports on Radxa ROCK 2A/2F Heiko Stuebner
2026-05-05 17:12 ` Heiko Stuebner
2026-05-05 17:12 ` [PATCH v2 4/5] arm64: dts: rockchip: Enable USB 2.0 ports on ArmSoM Sige1 Heiko Stuebner
2026-05-05 17:12 ` Heiko Stuebner
2026-05-25 7:00 ` Chukun Pan
2026-05-25 7:00 ` Chukun Pan
2026-05-28 22:12 ` Heiko Stuebner [this message]
2026-05-28 22:12 ` Heiko Stuebner
2026-05-05 17:12 ` [PATCH v2 5/5] arm64: dts: rockchip: Enable USB 2.0 ports on NanoPi Zero2 Heiko Stuebner
2026-05-05 17:12 ` Heiko Stuebner
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=6849370.F8r316W7xa@phil \
--to=heiko@sntech.de \
--cc=amadeus@jmu.edu.cn \
--cc=jonas@kwiboo.se \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.