From: sashiko-bot@kernel.org
To: "Jens Glathe" <jens.glathe@oldschoolsolutions.biz>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 5/5] arm64: dts: qcom: x1: disable ps883x USB4 capability
Date: Sat, 18 Jul 2026 17:22:37 +0000 [thread overview]
Message-ID: <20260718172238.3EE011F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260718-ps883x-disable-usb4-v1-5-cec86d0b909e@oldschoolsolutions.biz>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The `parade,disable-usb4` property encodes a transient software workaround into the Device Tree and breaks non-fallback docks by intentionally failing retimer configuration.
--
--- Patch [5]: [PATCH 5/5] arm64: dts: qcom: x1: disable ps883x USB4 capability ---
commit c967f56ff3b6574dc86834616a0288179a8a0cd3
Author: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
arm64: dts: qcom: x1: disable ps883x USB4 capability
Add the "parade,disable-usb4" property to the PS883x node so that the
retimer driver treats USB4 as USB3. This allows the combo PHY to remain
in a DP-capable mode, restoring working DisplayPort output over the
dock while keeping USB functional.
[ ... ]
> diff --git a/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi b/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi
> index 5d49df41be02a..c8bfb38c64ad5 100644
> --- a/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi
> +++ b/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi
> @@ -895,6 +895,8 @@ typec-mux@8 {
> orientation-switch;
> retimer-switch;
>
> + parade,disable-usb4;
[Severity: High]
The commit message mentions this is a temporary platform workaround for missing
software support. Does this encode a transient OS driver limitation into the
device tree?
Device trees typically describe fixed hardware capabilities. Will adding this
property permanently mask the hardware's actual capabilities and cause issues
for future OS updates once proper USB4 DP tunneling is available?
Also, looking at how the retimer driver handles this property:
drivers/usb/typec/mux/ps883x.c:ps883x_set() {
...
case TYPEC_MODE_USB4:
if (retimer->disable_usb4) {
dev_info(&retimer->client->dev,
"USB4 disabled via DT property, rejecting USB4 mode\n");
return -EOPNOTSUPP;
}
...
}
By returning -EOPNOTSUPP, this intentionally skips retimer configuration and
leaves the physical link broken. While some docks might detect the broken
link, time out, and fall back to DP Alt Mode + USB3, what happens with docks
that don't implement this fallback behavior?
Could this approach result in completely broken USB and DisplayPort
functionality on non-fallback docks when the PMIC autonomously negotiates
USB4?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260718-ps883x-disable-usb4-v1-0-cec86d0b909e@oldschoolsolutions.biz?part=5
prev parent reply other threads:[~2026-07-18 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 17:06 [PATCH 0/5] usb: typec: ps883x: fixes for older Thunderbolt 4 / USB4 docks Jens Glathe via B4 Relay
2026-07-18 17:06 ` [PATCH 1/5] dt-bindings: usb: parade,ps8830: Add parade,disable-usb4 property Jens Glathe via B4 Relay
2026-07-18 17:11 ` sashiko-bot
2026-07-18 17:06 ` [PATCH 2/5] usb: typec: ps883x: Return -EOPNOTSUPP for USB4 when parade,disable-usb4 is set Jens Glathe via B4 Relay
2026-07-18 17:14 ` sashiko-bot
2026-07-18 17:06 ` [PATCH 3/5] usb: typec: mux: ps883x: refactor DP altmode handling and support TYPEC_DP_STATE_F Jens Glathe via B4 Relay
2026-07-18 17:29 ` sashiko-bot
2026-07-18 17:06 ` [PATCH 4/5] usb: typec: mux: ps883x: add a delay after writing config regs Jens Glathe via B4 Relay
2026-07-18 17:06 ` [PATCH 5/5] arm64: dts: qcom: x1: disable ps883x USB4 capability Jens Glathe via B4 Relay
2026-07-18 17:22 ` sashiko-bot [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=20260718172238.3EE011F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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