From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bryan.Kemp@dell.com, tudor.laurentiu.oss@gmail.com
Subject: Re: [PATCH v1 1/1] arm64: dts: qcom: x1e80100-dell-xps13-9345: Introduce retimer support
Date: Mon, 4 Nov 2024 14:52:46 +0100 [thread overview]
Message-ID: <c1dbfe1e-9519-4bf9-81df-8c32e08d0126@oss.qualcomm.com> (raw)
In-Reply-To: <20241030182153.16256-2-alex.vinarskis@gmail.com>
On 30.10.2024 7:19 PM, Aleksandrs Vinarskis wrote:
> Describe x2 Parade PS8830 retimers for left and right USB Type-C ports
> respectively. Adjust graphs between connectors and the PHYs accordingly,
> add the voltage regulators. Dell XPS 13" 9345's DSDT describes 3rd
> retimer, but its not actually present.
>
> Regulators are _assumed_ to be correct, since:
> * tlmm pins match DSDT definition.
> * tlmm and pmic gpios were tested and confirmed to be powering
> off/resetting respective retimers.
> * USB3.0 now works correctly in both orientation, pre and post suspend.
>
> Derived from:
> arm64: dts: qcom: x1e80100-t14s: Add external DP support
>
> Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2024-11-04 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 18:19 [PATCH v1 0/1] X1E Dell XPS 9345 Improvements 2 Aleksandrs Vinarskis
2024-10-30 18:19 ` [PATCH v1 1/1] arm64: dts: qcom: x1e80100-dell-xps13-9345: Introduce retimer support Aleksandrs Vinarskis
2024-11-04 13:52 ` Konrad Dybcio [this message]
2024-10-31 2:28 ` [PATCH v1 0/1] X1E Dell XPS 9345 Improvements 2 Rob Herring (Arm)
2024-11-12 22:03 ` (subset) " Bjorn Andersson
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=c1dbfe1e-9519-4bf9-81df-8c32e08d0126@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=Bryan.Kemp@dell.com \
--cc=alex.vinarskis@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=tudor.laurentiu.oss@gmail.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