From: Xin Liu <xin.liu@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: 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>,
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>
Subject: Re: [PATCH v2] arm64: dts: qcom: hamoa-iot-evk: switch typec0 to PS8830 retimer
Date: Tue, 4 Aug 2026 15:04:58 +0800 [thread overview]
Message-ID: <58940156-c664-4ab2-835c-81fa43365bcd@oss.qualcomm.com> (raw)
In-Reply-To: <jx5iackeevtgqxycqbmctfohuydyarxxp4uqsu5dpihca5oc7m@gyyd6l67kzhx>
On 8/4/2026 3:35 AM, Dmitry Baryshkov wrote:
> On Mon, Aug 03, 2026 at 06:27:47AM -0700, Xin Liu wrote:
>> The Hamoa IoT EVK hardware design uses a Parade PS8830 retimer on
>> I2C3 for USB Type-C port 0. Describe the retimer and route typec0
>> through it to enable USB 3.0 SuperSpeed and DisplayPort Alt Mode.
>>
>> Supply the PS8830 from the existing vreg_rtmr0_* rails and remove
>> their stale "Left unused" annotation.
>>
>> The FSUSB42 SBU mux chip is present on the PCB but with all signal
>> lines unconnected (NC), so remove the fsusb42 node and its pinctrl
>> group.
> Why is it still present on the PCB?
The FSUSB42 is retained on the PCB as a fallback for the PS8830's SBU
mux function.
Should the PS8830's SBU path encounter any issues, the FSUSB42 can
be activated
with a simple rework to quickly switch to a discrete solution, avoiding
a full board respin.
Thanks,
Xin
>> Tested on the Hamoa IoT EVK:
>>
>> USB 3.0 SuperSpeed at 5 Gbps on typec0
>> DisplayPort Alt Mode on typec0
>>
>> Signed-off-by: Guodong Xu <guodong.xu@oss.qualcomm.com>
>> Signed-off-by: Xin Liu <xin.liu@oss.qualcomm.com>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>
>
next prev parent reply other threads:[~2026-08-04 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 13:27 Xin Liu
2026-08-03 19:35 ` Dmitry Baryshkov
2026-08-04 7:04 ` Xin Liu [this message]
2026-08-18 10:49 ` Konrad Dybcio
2026-09-03 7:55 ` 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=58940156-c664-4ab2-835c-81fa43365bcd@oss.qualcomm.com \
--to=xin.liu@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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=robh@kernel.org \
--cc=tingwei.zhang@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®