From: Joey Lu <a0987203069@gmail.com>
To: Jacky Huang <ychuang570808@gmail.com>,
Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Jacky Huang <ychuang3@nuvoton.com>,
Shan-Chun Hung <schung@nuvoton.com>,
Hui-Ping Chen <hpchen0nvt@gmail.com>, Joey Lu <yclu4@nuvoton.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] arm64: dts: nuvoton: ma35d1: add USB controllers and dual-port PHY node
Date: Thu, 24 Sep 2026 14:48:08 +0800 [thread overview]
Message-ID: <0e6fb86c-e995-4ef1-b08b-44a5e8be93f9@gmail.com> (raw)
In-Reply-To: <2d07e535-3029-41d0-9dcf-8772f7330434@gmail.com>
Jacky Huang 於 2026/9/19 下午 01:49 寫道:
>> Add the USB subsystem nodes for the MA35D1 SoC and boards:
>>
>> - usb_phy: standalone PHY node with #phy-cells = <1>, covering both
>> the OTG port (PHY0, index 0) and the host-only port (PHY1, index
>> 1).
>> Uses nuvoton,sys phandle and HUSBH0_GATE clock per the binding.
>>
>> - usb (DWC2 gadget, USB0): phys = <&usb_phy 0>, dr_mode = peripheral.
>> - ehci0/ohci0 (USB0 host): phys = <&usb_phy 0>, companion pairing.
>> - ehci1/ohci1 (USB1 host): phys = <&usb_phy 1>.
>>
>> Board files (ma35d1-som-256m.dts, ma35d1-iot-512m.dts) add pinctrl for
>> VBUSVLD, PWREN and OVC signals and enable all USB nodes.
>>
>> Signed-off-by: Joey Lu <a0987203069@gmail.com>
>> ---
>> .../boot/dts/nuvoton/ma35d1-iot-512m.dts | 36 ++++++++++
>> .../boot/dts/nuvoton/ma35d1-som-256m.dts | 36 ++++++++++
>> arch/arm64/boot/dts/nuvoton/ma35d1.dtsi | 65 +++++++++++++++++++
>> 3 files changed, 137 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/nuvoton/ma35d1-iot-512m.dts
>> b/arch/arm64/boot/dts/nuvoton/ma35d1-iot-512m.dts
>> index 78534d613486..0a068abda6e0 100644
>> --- a/arch/arm64/boot/dts/nuvoton/ma35d1-iot-512m.dts
>> +++ b/arch/arm64/boot/dts/nuvoton/ma35d1-iot-512m.dts
>> @@ -97,6 +97,16 @@ pinctrl_uart14: uart14-pins {
>> power-source = <1>;
>> };
>> };
>> +
>> + hsusb {
>> + pinctrl_hsusb: hsusb-pins {
>> + nuvoton,pins = <5 15 1>, /* VBUSVLD */
>> + <11 12 9>, /* PWREN */
>> + <11 13 9>; /* OVC */
>> + bias-disable;
>> + power-source = <1>;
>> + };
>> + };
>> };
>>
>
> The outer pinctrl group node name does not match the MA35D1 pinctrl
> binding. dt-validate reports:
>
> 'hsusb' does not match any of the regexes: '-grp$',
> '^gpio@[0-9a-f]+$', '^pinctrl-[0-9]+$'
>
> Please rename it to "hsusb-grp" in both ma35d1-iot-512m.dts and
> ma35d1-som-256m.dts.
>
> I tested this change locally. Both affected DTBs build and validate
> cleanly after the rename.
>
>
> Best regards,
> Jacky Huang
Agreed, hsusb doesn't match the pinctrl node-name regex. I'll rename it
to hsusb-grp in both
ma35d1-iot-512m.dts and ma35d1-som-256m.dts in the next revision.
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Joey Lu <a0987203069@gmail.com>
To: Jacky Huang <ychuang570808@gmail.com>,
Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Jacky Huang <ychuang3@nuvoton.com>,
Shan-Chun Hung <schung@nuvoton.com>,
Hui-Ping Chen <hpchen0nvt@gmail.com>, Joey Lu <yclu4@nuvoton.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] arm64: dts: nuvoton: ma35d1: add USB controllers and dual-port PHY node
Date: Thu, 24 Sep 2026 14:48:08 +0800 [thread overview]
Message-ID: <0e6fb86c-e995-4ef1-b08b-44a5e8be93f9@gmail.com> (raw)
In-Reply-To: <2d07e535-3029-41d0-9dcf-8772f7330434@gmail.com>
Jacky Huang 於 2026/9/19 下午 01:49 寫道:
>> Add the USB subsystem nodes for the MA35D1 SoC and boards:
>>
>> - usb_phy: standalone PHY node with #phy-cells = <1>, covering both
>> the OTG port (PHY0, index 0) and the host-only port (PHY1, index
>> 1).
>> Uses nuvoton,sys phandle and HUSBH0_GATE clock per the binding.
>>
>> - usb (DWC2 gadget, USB0): phys = <&usb_phy 0>, dr_mode = peripheral.
>> - ehci0/ohci0 (USB0 host): phys = <&usb_phy 0>, companion pairing.
>> - ehci1/ohci1 (USB1 host): phys = <&usb_phy 1>.
>>
>> Board files (ma35d1-som-256m.dts, ma35d1-iot-512m.dts) add pinctrl for
>> VBUSVLD, PWREN and OVC signals and enable all USB nodes.
>>
>> Signed-off-by: Joey Lu <a0987203069@gmail.com>
>> ---
>> .../boot/dts/nuvoton/ma35d1-iot-512m.dts | 36 ++++++++++
>> .../boot/dts/nuvoton/ma35d1-som-256m.dts | 36 ++++++++++
>> arch/arm64/boot/dts/nuvoton/ma35d1.dtsi | 65 +++++++++++++++++++
>> 3 files changed, 137 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/nuvoton/ma35d1-iot-512m.dts
>> b/arch/arm64/boot/dts/nuvoton/ma35d1-iot-512m.dts
>> index 78534d613486..0a068abda6e0 100644
>> --- a/arch/arm64/boot/dts/nuvoton/ma35d1-iot-512m.dts
>> +++ b/arch/arm64/boot/dts/nuvoton/ma35d1-iot-512m.dts
>> @@ -97,6 +97,16 @@ pinctrl_uart14: uart14-pins {
>> power-source = <1>;
>> };
>> };
>> +
>> + hsusb {
>> + pinctrl_hsusb: hsusb-pins {
>> + nuvoton,pins = <5 15 1>, /* VBUSVLD */
>> + <11 12 9>, /* PWREN */
>> + <11 13 9>; /* OVC */
>> + bias-disable;
>> + power-source = <1>;
>> + };
>> + };
>> };
>>
>
> The outer pinctrl group node name does not match the MA35D1 pinctrl
> binding. dt-validate reports:
>
> 'hsusb' does not match any of the regexes: '-grp$',
> '^gpio@[0-9a-f]+$', '^pinctrl-[0-9]+$'
>
> Please rename it to "hsusb-grp" in both ma35d1-iot-512m.dts and
> ma35d1-som-256m.dts.
>
> I tested this change locally. Both affected DTBs build and validate
> cleanly after the rename.
>
>
> Best regards,
> Jacky Huang
Agreed, hsusb doesn't match the pinctrl node-name regex. I'll rename it
to hsusb-grp in both
ma35d1-iot-512m.dts and ma35d1-som-256m.dts in the next revision.
Thanks.
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-09-24 6:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 3:18 [PATCH v5 0/3] phy: nuvoton: extend MA35D1 USB2 PHY driver for dual-port OTG support Joey Lu
2026-09-14 3:18 ` Joey Lu
2026-09-14 3:18 ` [PATCH v5 1/3] dt-bindings: phy: nuvoton,ma35d1-usb2-phy: extend for dual-port and OTG Joey Lu
2026-09-14 3:18 ` Joey Lu
2026-09-14 3:18 ` [PATCH v5 2/3] arm64: dts: nuvoton: ma35d1: add USB controllers and dual-port PHY node Joey Lu
2026-09-14 3:18 ` Joey Lu
2026-09-19 5:49 ` Jacky Huang
2026-09-19 5:49 ` Jacky Huang
2026-09-24 6:48 ` Joey Lu [this message]
2026-09-24 6:48 ` Joey Lu
2026-09-14 3:18 ` [PATCH v5 3/3] phy: nuvoton: phy-ma35d1-usb2: extend to dual-port with OTG support Joey Lu
2026-09-14 3:18 ` Joey Lu
2026-09-14 3:27 ` sashiko-bot
2026-09-14 3:27 ` sashiko-bot
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=0e6fb86c-e995-4ef1-b08b-44a5e8be93f9@gmail.com \
--to=a0987203069@gmail.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hpchen0nvt@gmail.com \
--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=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=schung@nuvoton.com \
--cc=vkoul@kernel.org \
--cc=ychuang3@nuvoton.com \
--cc=ychuang570808@gmail.com \
--cc=yclu4@nuvoton.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 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.