From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Xin Liu <xin.liu@oss.qualcomm.com>,
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, tingwei.zhang@oss.qualcomm.com,
jie.gan@oss.qualcomm.com,
Guodong Xu <guodong.xu@oss.qualcomm.com>,
Milosz Wasilewski <milosz.wasilewski@oss.qualcomm.com>
Subject: Re: [PATCH] arm64: dts: qcom: hamoa-iot-evk: switch typec0 to PS8830 retimer
Date: Tue, 21 Jul 2026 16:28:18 +0200 [thread overview]
Message-ID: <70349e4e-12d4-4cc4-91dd-9e5d45d3427b@oss.qualcomm.com> (raw)
In-Reply-To: <20260721074145.1534100-1-xin.liu@oss.qualcomm.com>
On 7/21/26 9:41 AM, Xin Liu wrote:
> The Hamoa IoT EVK populates a Parade PS8830 retimer on I2C3 for the
> TypeC 0 port to support USB3.0 and SBU muxing. Describe the PS8830 and
> route typec0 through it.
>
> The vreg_rtmr0_* rails provisioned for a retimer were already defined
> but previously wired to nowhere. They are now consumed by the PS8830,
> so drop the "Left unused" comment.
>
> The FSUSB42 SBU mux chip won't be populated on the final EVK
> board, so remove the fsusb42 node and its pinctrl group.
Are we sure about that? I inquired about this on a pre-release
version of an equivalent patch and never got an answer. For sure
there are a number of boards without a retimer, including in our CI
(+CC Miłosz)..
Konrad
next prev parent reply other threads:[~2026-07-21 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 7:41 Xin Liu
2026-07-21 14:28 ` Konrad Dybcio [this message]
2026-08-03 6:03 ` Xin Liu
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=70349e4e-12d4-4cc4-91dd-9e5d45d3427b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guodong.xu@oss.qualcomm.com \
--cc=jie.gan@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milosz.wasilewski@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=xin.liu@oss.qualcomm.com \
/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®