From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, Chaoyi Chen <kernel@airkyi.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Quentin Schulz <quentin.schulz@cherry.de>,
Jonas Karlman <jonas@kwiboo.se>, Hsun Lai <i@chainsx.cn>,
John Clark <inindev@gmail.com>, Jimmy Hon <honyuenkwun@gmail.com>,
Dragan Simic <dsimic@manjaro.org>,
Michael Riesch <michael.riesch@collabora.com>,
Peter Robinson <pbrobinson@gmail.com>,
Alexey Charkov <alchark@gmail.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Andy Yan <andy.yan@rock-chips.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: usb: Add binding for WCH CH334/CH335 hub controller
Date: Mon, 12 Jan 2026 16:59:01 +0800 [thread overview]
Message-ID: <1515a445-576a-4833-a604-c31062f7d3fa@rock-chips.com> (raw)
In-Reply-To: <20260112-lively-hallowed-beetle-fc15b2@quoll>
Hi Krzysztof,
On 1/12/2026 4:50 PM, Krzysztof Kozlowski wrote:
> On Mon, Jan 12, 2026 at 10:28:21AM +0800, Chaoyi Chen wrote:
>> From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
>>
>> The WCH CH334/CH335[0] are USB2.0 protocol compliant 4-port USB HUB
>> controller chips, supporting USB2.0 high-speed and full-speed for
>> upstream ports, and USB2.0 high-speed 480Mbps, full-speed 12Mbps and
>> low-speed 1.5Mbps for downstream ports, supporting not only low-cost STT
>> mode (single TT schedules 4 downstream ports in time share), but also
>> supports high performance MTT mode (4 TTs each corresponding to 1 port,
>> concurrent processing).
>>
>> Add a device tree binding for it.
>>
>> [0]: https://www.wch-ic.com/downloads/CH334DS1_PDF.html
>>
>> Signed-off-by: Chaoyi Chen <chaoyi.chen@rock-chips.com>
>> ---
>> .../devicetree/bindings/usb/wch,ch334.yaml | 65 +++++++++++++++++++
>
> This must be separate patch. Do not combine independent subsystems into
> one patchset.
>
Okay, thank you for the reminder.
>> 1 file changed, 65 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/usb/wch,ch334.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/usb/wch,ch334.yaml b/Documentation/devicetree/bindings/usb/wch,ch334.yaml
>> new file mode 100644
>> index 000000000000..2eeb92f25b4c
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/usb/wch,ch334.yaml
>> @@ -0,0 +1,65 @@
>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/usb/wch,ch334.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: WCH CH334/CH335 USB 2.0 Hub Controller
>> +
>> +maintainers:
>> + - Chaoyi Chen <kernel@airkyi.com>
>> +
>> +allOf:
>> + - $ref: usb-hub.yaml#
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - usb1a86,8091
>> +
>> + reg: true
>> +
>> + reset-gpios:
>> + description: GPIO controlling the RESET# pin.
>> +
>> + vdd-supply:
>> + description:
>> + The regulator that provides 3.3V core power to the hub.
>> +
>> + vdd2-supply:
>> + description:
>> + The regulator that provides 3.3V or 5V power to the hub.
>> +
>> + ports:
>> + $ref: /schemas/graph.yaml#/properties/ports
>> +
>> + patternProperties:
>> + '^port@':
>> + $ref: /schemas/graph.yaml#/properties/port
>> +
>> + properties:
>> + reg:
>> + minimum: 1
>> + maximum: 4
>> +
>> +required:
>> + - compatible
>> + - reg
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/gpio/gpio.h>
>> + usb {
>> + dr_mode = "host";
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + hub: hub@1 {
>> + compatible = "usb1a86,8091";
>> + reg = <1>;
>> + reset-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
>
> Are you sure?
I guess what you're concerned about here is the polarity?
If that's the case, then there's no problem.
--
Best,
Chaoyi
next prev parent reply other threads:[~2026-01-12 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 2:28 [PATCH v3 0/3] arm64: dts: rockchip: Add rk3576 evb2 board Chaoyi Chen
2026-01-12 2:28 ` [PATCH v3 1/3] dt-bindings: usb: Add binding for WCH CH334/CH335 hub controller Chaoyi Chen
2026-01-12 8:50 ` Krzysztof Kozlowski
2026-01-12 8:59 ` Chaoyi Chen [this message]
2026-01-12 14:28 ` Krzysztof Kozlowski
2026-01-13 3:27 ` Chaoyi Chen
2026-01-13 3:45 ` Chaoyi Chen
2026-01-13 7:41 ` Krzysztof Kozlowski
2026-01-12 14:00 ` Quentin Schulz
2026-01-13 3:38 ` Chaoyi Chen
2026-01-12 2:28 ` [PATCH v3 2/3] dt-bindings: arm: rockchip: Add rk3576 evb2 board Chaoyi Chen
2026-01-12 2:28 ` [PATCH v3 3/3] arm64: dts: " Chaoyi Chen
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=1515a445-576a-4833-a604-c31062f7d3fa@rock-chips.com \
--to=chaoyi.chen@rock-chips.com \
--cc=alchark@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=honyuenkwun@gmail.com \
--cc=i@chainsx.cn \
--cc=inindev@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@airkyi.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.riesch@collabora.com \
--cc=pbrobinson@gmail.com \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.lin@rock-chips.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
all inboxes | Powered by JetHome®