From: Quentin Schulz <quentin.schulz@cherry.de>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
vkoul@kernel.org, kishon@kernel.org,
linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
christophe.jaillet@wanadoo.fr,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH v2 2/2] phy: rockchip: usbdp: re-init the phy on orientation-change
Date: Mon, 3 Mar 2025 10:27:31 +0100 [thread overview]
Message-ID: <2af85aa0-96dc-43ea-9542-88f91b21a028@cherry.de> (raw)
In-Reply-To: <dkjpudmzuuxvaotz4mx46yx7iacof7q6ck746j3rrqvlgbq3hk@6vtvy3gy3kff>
Hi Sebastian,
On 3/1/25 10:19 PM, Sebastian Reichel wrote:
> Hello Quentin,
>
> On Wed, Feb 26, 2025 at 01:38:10PM +0100, Quentin Schulz wrote:
>> Unrelated to this patch (but may be triggered by this patch?), I'm wondering
>> how flip is really handled.
>>
>> It seems like we have flip store the orientation of the cable, but also if
>> rockchip,dp-lane-mux is set to <0 1>. But wouldn't that break if we ignore
>> that initial flipped lane-mux whenever a USB-C cable is inserted in reverse?
>> Basically, shouldn't a reserve orientation of the cable when
>> rockchip,dp-lane-mux is set to <0 1> mean "normal mux"?
>
> If a USB-C connector is involved, the TypeC controller is supposed to
> setup the lane muxing based on the connector orientation. This
> happens via the typec API and in this hardware setup the PHY should
> not have the rockchip,dp-lane-mux DT property set.
>
I could see some HW routing "mistake" where the USB-C connector in
normal orientation has DP lanes routed to RX1/TX1? Or is this expected
to just be faulty HW we shouldn't attempt at supporting?
> The rockchip,dp-lane-mux property is required if no USB-C connector
> is involved. For example if the lanes are routed to a Displayport
> connector. In that case the lane setup is fixed in hardware and
> there is no TypeC controller involved, which could do any setup ;)
>
Yup I've seen that for the Rock 5 ITX and the evaluation board(s) do
this. Quite interesting :)
Cheers,
Quentin
next prev parent reply other threads:[~2025-03-03 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 10:38 [PATCH v2 0/2] phy: rockchip: usbdp: improve typec orientation handling Heiko Stuebner
2025-02-26 10:38 ` [PATCH v2 1/2] phy: rockchip: usbdp: move type-orientation-switch further down Heiko Stuebner
2025-02-26 11:43 ` Quentin Schulz
2025-02-26 10:38 ` [PATCH v2 2/2] phy: rockchip: usbdp: re-init the phy on orientation-change Heiko Stuebner
2025-02-26 12:38 ` Quentin Schulz
2025-03-01 21:19 ` Sebastian Reichel
2025-03-03 9:27 ` Quentin Schulz [this message]
2025-03-05 21:52 ` Sebastian Reichel
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=2af85aa0-96dc-43ea-9542-88f91b21a028@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=sebastian.reichel@collabora.com \
--cc=vkoul@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®