From: Chaoyi Chen <kernel@airkyi.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Catalin Popescu" <catalin.popescu@leica-geosystems.com>,
"Stephen Boyd" <swboyd@chromium.org>,
"Jens Glathe" <jens.glathe@oldschoolsolutions.biz>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Mike Looijmans" <mike.looijmans@topic.nl>,
"Pin-yen Lin" <treapking@chromium.org>,
"J. Neuschäfer" <j.ne@posteo.net>,
"Quentin Schulz" <quentin.schulz@cherry.de>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chaoyi Chen <chaoyi.chen@rock-chips.com>
Subject: [PATCH v2 0/2] usb: misc: onboard_dev: Add WCH CH334 USB2.0 Hub (1a86:8091)
Date: Tue, 13 Jan 2026 17:58:25 +0800 [thread overview]
Message-ID: <20260113095827.115-1-kernel@airkyi.com> (raw)
From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
Hi,
This series add support for WCH CH334/CH335 USB2.0 Hub (1a86:8091).
Changes in v2:
- Link to v1: https://lore.kernel.org/all/20260112022823.91-2-kernel@airkyi.com/
- Add missing driver (PATCH 2).
- Fix the incorrect reset GPIO polarity.
- Use a more meaningful supply name.
Chaoyi Chen (2):
dt-bindings: usb: Add binding for WCH CH334/CH335 hub controller
usb: misc: onboard_dev: Add WCH CH334 USB2.0 Hub (1a86:8091)
.../devicetree/bindings/usb/wch,ch334.yaml | 65 +++++++++++++++++++
drivers/usb/misc/onboard_usb_dev.h | 8 +++
2 files changed, 73 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/wch,ch334.yaml
--
2.51.1
next reply other threads:[~2026-01-13 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 9:58 Chaoyi Chen [this message]
2026-01-13 9:58 ` [PATCH v2 1/2] dt-bindings: usb: Add binding for WCH CH334/CH335 hub controller Chaoyi Chen
2026-01-15 18:49 ` Rob Herring (Arm)
2026-01-13 9:58 ` [PATCH v2 2/2] usb: misc: onboard_dev: Add WCH CH334 USB2.0 Hub (1a86:8091) 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=20260113095827.115-1-kernel@airkyi.com \
--to=kernel@airkyi.com \
--cc=catalin.popescu@leica-geosystems.com \
--cc=chaoyi.chen@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=j.ne@posteo.net \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=swboyd@chromium.org \
--cc=treapking@chromium.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