From: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>
To: Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
Subject: Re: [PATCH] dt: arm64: qcom: sc8280xp-blackrock: amend usb0-sbu-mux enable gpio
Date: Sun, 17 May 2026 12:03:29 +0200 [thread overview]
Message-ID: <25464c46-4576-4411-a7a0-4ad950605ad5@gmail.com> (raw)
In-Reply-To: <20250609-blackrock-usb0-mux-v1-1-7903c3b071e4@oldschoolsolutions.biz>
On 6/9/25 22:53, Jens Glathe wrote:
> The usb0 port didn't switch to dp altmode, investigation into DSDT
> UCS0 device resulted into GPIO 100.
>
> Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Tested:by: Jérome de Bretagne <jerome.debretagne@gmail.com>
The same issue was impacting the other sc8280xp-based model from
Microsoft, which is sharing an almost identical board:
The top USB-C port (usb0) didn't switch to DP alt mode, as reusing the
same GPIO 101 as on the SC8280XP CRD or Lenovo ThinkPad X13s was not
working on the Surface Pro 9 5G (arcata) either.
Switching to GPIO 100 fixed the issue on arcata as well, to finally.
enable external screen when using the left-side top USB-C port. I
will send the fix for the Surface Pro 9 5G as part of a series
fixing various issues and limitations in its initial device tree.
Thank you,
Jérôme
next prev parent reply other threads:[~2026-05-17 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 20:53 [PATCH] dt: arm64: qcom: sc8280xp-blackrock: amend usb0-sbu-mux enable gpio Jens Glathe via B4 Relay
2026-05-17 10:03 ` Jérôme de Bretagne [this message]
2026-05-17 10:09 ` Jérôme de Bretagne
2026-05-17 11:59 ` Dmitry Baryshkov
2026-05-18 7:50 ` Konrad Dybcio
2026-05-18 8:18 ` Jens Glathe
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=25464c46-4576-4411-a7a0-4ad950605ad5@gmail.com \
--to=jerome.debretagne@gmail.com \
--cc=alex.vinarskis@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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