From: Alexey Charkov <alchark@flipper.net>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Gene Chen <gene_chen@richtek.com>,
Heiko Stuebner <heiko@sntech.de>
Cc: Sebastian Reichel <sebastian.reichel@collabora.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Alexey Charkov <alchark@flipper.net>
Subject: [PATCH 0/4] Add HUSB311 Type-C controller
Date: Wed, 11 Mar 2026 20:20:43 +0400 [thread overview]
Message-ID: <20260311-husb311-v1-0-f25bcb58cff7@flipper.net> (raw)
HUSB311 is a drop-in replacement for RT1711H, used in Rockchip RK3576 EVB1
board and some other boards closely following the reference schematic.
The existing RT1711H driver seems to work fine with HUSB311, and there is
no public documentation available for HUSB311 to identify any meaningful
differences, so this series wires up the existing driver to treat
HUSB311 in the same way it treats RT1711H.
This also enables a bare-bones DT node for HUSB311 on RK3576 EVB1, but
currently misses the connections graph for the USB SS and SBU lines, as
those might require the USBDP PHY ports schema to be updated first for
proper DP AltMode support as indicated by Sebastian.
Signed-off-by: Alexey Charkov <alchark@flipper.net>
---
Alexey Charkov (4):
dt-bindings: vendor-prefixes: Add Hynetek Semiconductor Co., Ltd.
dt-bindings: usb: richtek,rt1711h: Add Hynetek HUSB311
usb: typec: tcpci_rt1711h: Add support for Hynetek HUSB311
arm64: dts: rockchip: Add HUSB311 Type-C controller on RK3576 EVB1
.../devicetree/bindings/usb/richtek,rt1711h.yaml | 2 ++
.../devicetree/bindings/vendor-prefixes.yaml | 2 ++
arch/arm64/boot/dts/rockchip/rk3576-evb1-v10.dts | 20 ++++++++++++++++++++
drivers/usb/typec/tcpm/tcpci_rt1711h.c | 21 +++++++++++++++++++--
4 files changed, 43 insertions(+), 2 deletions(-)
---
base-commit: 7109a2155340cc7b21f27e832ece6df03592f2e8
change-id: 20260115-husb311-291bbb1a7776
Best regards,
--
Alexey Charkov <alchark@flipper.net>
next reply other threads:[~2026-03-11 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 16:20 Alexey Charkov [this message]
2026-03-11 16:20 ` [PATCH 1/4] dt-bindings: vendor-prefixes: Add Hynetek Semiconductor Co., Ltd Alexey Charkov
2026-03-11 18:30 ` Conor Dooley
2026-03-11 16:20 ` [PATCH 2/4] dt-bindings: usb: richtek,rt1711h: Add Hynetek HUSB311 Alexey Charkov
2026-03-11 16:20 ` [PATCH 3/4] usb: typec: tcpci_rt1711h: Add support for " Alexey Charkov
2026-03-11 18:32 ` Conor Dooley
2026-03-12 7:09 ` Alexey Charkov
2026-03-12 11:17 ` Conor Dooley
2026-03-11 16:20 ` [PATCH 4/4] arm64: dts: rockchip: Add HUSB311 Type-C controller on RK3576 EVB1 Alexey Charkov
2026-03-11 18:32 ` [PATCH 0/4] Add HUSB311 Type-C controller Dragan Simic
2026-03-12 6:54 ` Alexey Charkov
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=20260311-husb311-v1-0-f25bcb58cff7@flipper.net \
--to=alchark@flipper.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gene_chen@richtek.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=heiko@sntech.de \
--cc=krzk+dt@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=robh@kernel.org \
--cc=sebastian.reichel@collabora.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