mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Alexey Charkov <alchark@flipper.net>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: Describe the Type-C port on RK3576 EVB1
Date: Thu, 12 Nov 2026 09:01:29 +0800	[thread overview]
Message-ID: <dd25880e-be2d-4adc-8384-fa4a7160a4df@rock-chips.com> (raw)
In-Reply-To: <CAKTNdwHbxnknob9NdjqWUcGU2fURO5B7V4kTTK+fvEYjNDOLCA@mail.gmail.com>

Hi Alexey,

On 11/11/2026 6:45 PM, Alexey Charkov wrote:
> Hi Chaoyi,
> 
> On Wed, Nov 11, 2026 at 1:31 PM Chaoyi Chen <chaoyi.chen@rock-chips.com> wrote:
>>
>> Hi Alexey,
>>
>> On 11/7/2026 1:52 AM, Alexey Charkov wrote:
>>> RK3576 EVB1 has its USBDP PHY routed to a Type-C port with a HUSB311 CC
>>> controller and a fixed-voltage VBUS supply.
>>>
>>> Describe it in the device tree, including the wiring for both the USB and
>>> the DP side.
>>>
>>> This makes the data roles follow the Type-C port's negotiation, so the
>>> port stops being host only. It also leaves the VBUS regulator to be
>>> managed by TCPM instead of being hardwired via the tangentially related
>>> phy-supply on a USB controller. DP lanes are also muxed dynamically by
>>> the USBDP PHY based on the Type-C port's negotiation, so the hacky fixed
>>> lane muxing also goes away.
>>>
>>
>> Have you tested this? As far as I know, dw-dp driver does not support
>> Type-C HPD yet.
> 
> I did - it works fine for me under Linux with Sebastian's patches. My
> primary motivation, however, was U-Boot, where the current phy-supply
> hack breaks USB data role switching, due to VBUS being forced
> always-on. With this patch it works, and now the DT actually describes
> the hardware, as it is supposed to.
> 

Oh, I almost forgot about that. I think it should be this patch series[0], right?

But I think we probably need more than just this series, because
richtek,rt1711h does not register the HPD bridge, so we will get this:

[   14.828983] auxiliary aux_bridge.aux_bridge.0: deferred probe pending: aux_bridge.aux_bridge: failed to acquire drm_bridge

Maybe you have already added the corresponding patch yourself?
Another option is to use the generic AUX HPD patch[1]. :)

[0]: https://lore.kernel.org/linux-rockchip/20260806-synopsys-dw-dp-improvements-v11-0-0d508505f383@collabora.com/
[1]: https://lore.kernel.org/all/20261020072816.180-1-kernel@airkyi.com/

-- 
Best, 
Chaoyi

      reply	other threads:[~2026-11-12  1:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 17:52 Alexey Charkov
2026-11-11  9:31 ` Chaoyi Chen
2026-11-11 10:45   ` Alexey Charkov
2026-11-12  1:01     ` Chaoyi Chen [this message]

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=dd25880e-be2d-4adc-8384-fa4a7160a4df@rock-chips.com \
    --to=chaoyi.chen@rock-chips.com \
    --cc=alchark@flipper.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=robh@kernel.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

all inboxes | Powered by JetHome®