From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: Kever Yang <kever.yang@rock-chips.com>,
Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Eugen Hristev <eugen.hristev@linaro.org>,
Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH] rockchip: rk3588-rock-5b: Remove USB-C controller from u-boot.dtsi
Date: Mon, 26 Jan 2026 23:09:13 +0100 [thread overview]
Message-ID: <aXfl19X8PMzlEARg@venus> (raw)
In-Reply-To: <20260126215601.837587-1-jonas@kwiboo.se>
[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]
Hi,
On Mon, Jan 26, 2026 at 09:55:59PM +0000, Jonas Karlman wrote:
> The commit 12049db76437 ("rockchip: rk3588-rock-5b: Add USB-C controller
> to u-boot.dtsi") added the USB-C controller node to the ROCK 5B board
> u-boot.dtsi, this and related usb nodes are now part of upstream DT.
>
> Remove the upstream USB-C controller related DT nodes from u-boot.dtsi,
> keep usbc0 status = "okay" to keep USB-C power delivery working.
>
> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
> ---
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Greetings,
-- Sebastian
> arch/arm/dts/rk3588-rock-5b-u-boot.dtsi | 43 +------------------------
> 1 file changed, 1 insertion(+), 42 deletions(-)
>
> diff --git a/arch/arm/dts/rk3588-rock-5b-u-boot.dtsi b/arch/arm/dts/rk3588-rock-5b-u-boot.dtsi
> index e07b549c767f..ddc177344ebd 100644
> --- a/arch/arm/dts/rk3588-rock-5b-u-boot.dtsi
> +++ b/arch/arm/dts/rk3588-rock-5b-u-boot.dtsi
> @@ -19,33 +19,6 @@
> bootph-some-ram;
> };
>
> -&i2c4 {
> - pinctrl-names = "default";
> - pinctrl-0 = <&i2c4m1_xfer>;
> - status = "okay";
> -
> - usbc0: usb-typec@22 {
> - compatible = "fcs,fusb302";
> - reg = <0x22>;
> - interrupt-parent = <&gpio3>;
> - interrupts = <RK_PB4 IRQ_TYPE_LEVEL_LOW>;
> - pinctrl-names = "default";
> - status = "okay";
> -
> - usb_con: connector {
> - compatible = "usb-c-connector";
> - label = "USB-C";
> - data-role = "dual";
> - power-role = "sink";
> - try-power-role = "sink";
> - op-sink-microwatt = <1000000>;
> - sink-pdos =
> - <PDO_FIXED(5000, 3000, PDO_FIXED_USB_COMM)>,
> - <PDO_VAR(5000, 20000, 5000)>;
> - };
> - };
> -};
> -
> &saradc {
> bootph-pre-ram;
> vdd-microvolts = <1800000>;
> @@ -63,20 +36,6 @@
> };
> };
>
> -&u2phy0 {
> - status = "okay";
> -};
> -
> -&u2phy0_otg {
> - status = "okay";
> -};
> -
> -&usbdp_phy0 {
> - status = "okay";
> -};
> -
> -&usb_host0_xhci {
> - dr_mode = "peripheral";
> - maximum-speed = "high-speed";
> +&usbc0 {
> status = "okay";
> };
> --
> 2.52.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-26 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 21:55 [PATCH] rockchip: rk3588-rock-5b: Remove USB-C controller from u-boot.dtsi Jonas Karlman
2026-01-26 22:09 ` Sebastian Reichel [this message]
2026-02-13 17:17 ` Quentin Schulz
2026-02-13 17:42 ` Jonas Karlman
2026-02-16 9:21 ` Quentin Schulz
2026-03-09 3:02 ` Kever Yang
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=aXfl19X8PMzlEARg@venus \
--to=sebastian.reichel@collabora.com \
--cc=eugen.hristev@linaro.org \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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