From: Wei Xu <xuwei5@hisilicon.com>
To: Akash Sukhavasi <akash.sukhavasi@gmail.com>
Cc: <krzk+dt@kernel.org>, <robh@kernel.org>, <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<xuwei5@hisilicon.com>
Subject: Re: [PATCH] arm64: dts: hisilicon: hi3660-hikey960: move role-switch endpoint into connector
Date: Thu, 4 Jun 2026 16:48:31 +0800 [thread overview]
Message-ID: <6A213BDF.9060202@hisilicon.com> (raw)
In-Reply-To: <aiBVHbRX3wxUNFs2@gmail.com>
Hi Akash,
On 2026/6/4 2:54, Akash Sukhavasi wrote:
> On Wed, May 20, 2026 at 04:53:25PM -0500, Akash Sukhavasi wrote:
>> The rt1711h Type-C controller on the HiKey960 has the USB role-switch
>> endpoint placed as a top-level 'port' node, outside the connector
>> subnode. This triggers two dtbs_check warnings against
>> richtek,rt1711h.yaml:
>>
>> - 'port' does not match any of the regexes: '^pinctrl-[0-9]+$'
>> - connector:ports: 'port@0' is a required property
>>
>> Move the role-switch endpoint into the connector's port@0, which is
>> where usb-connector.yaml expects it. Update the DWC3 remote-endpoint
>> phandle accordingly.
>>
>> The TCPM core (tcpm.c) looks up the role switch starting from the
>> connector fwnode via fwnode_usb_role_switch_get(). With the endpoint
>> inside the connector's port@0, it is found through the primary lookup
>> path rather than the device-level fallback.
>>
>> Cross-compiled for arm64. Verified with dt_binding_check and
>> dtbs_check. Not runtime-tested on hardware.
>>
>> Signed-off-by: Akash Sukhavasi <akash.sukhavasi@gmail.com>
>> ---
>> .../boot/dts/hisilicon/hi3660-hikey960.dts | 17 +++++++----------
>> 1 file changed, 7 insertions(+), 10 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts b/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts
>> index c6056a85c..27fb08d34 100644
>> --- a/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts
>> +++ b/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts
>> @@ -550,6 +550,12 @@ usb_con: connector {
>> ports {
>> #address-cells = <1>;
>> #size-cells = <0>;
>> + port@0 {
>> + reg = <0>;
>> + usb_con_hs: endpoint {
>> + remote-endpoint = <&dwc3_role_switch>;
>> + };
>> + };
>> port@1 {
>> reg = <1>;
>> usb_con_ss: endpoint {
>> @@ -558,15 +564,6 @@ usb_con_ss: endpoint {
>> };
>> };
>> };
>> - port {
>> - #address-cells = <1>;
>> - #size-cells = <0>;
>> -
>> - rt1711h_ep: endpoint@0 {
>> - reg = <0>;
>> - remote-endpoint = <&dwc3_role_switch>;
>> - };
>> - };
>> };
>>
>> adv7533: adv7533@39 {
>> @@ -683,7 +680,7 @@ port {
>> #size-cells = <0>;
>> dwc3_role_switch: endpoint@0 {
>> reg = <0>;
>> - remote-endpoint = <&rt1711h_ep>;
>> + remote-endpoint = <&usb_con_hs>;
>> };
>>
>> dwc3_ss: endpoint@1 {
>> --
>
> Hi Wei,
>
> Friendly ping on this one.
> Also, is the hikey960 board still actively taking fixes?
>
Sorry for the late reply!
Fine to me and applied to the HiSilicon arm64 dt tree.
Thanks!
Best Regards,
Wei
prev parent reply other threads:[~2026-06-04 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 21:53 [PATCH] arm64: dts: hisilicon: hi3660-hikey960: move role-switch endpoint into connector Akash Sukhavasi
2026-06-03 18:54 ` Akash Sukhavasi
2026-06-04 8:48 ` Wei Xu [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=6A213BDF.9060202@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=akash.sukhavasi@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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