From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
Pengyu Luo <mitltlatltl@gmail.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, Xilin Wu <sophon@radxa.com>
Subject: Re: [PATCH] arm64: dts: qcom: sc8280xp: correct usb phy power supply
Date: Thu, 21 May 2026 11:25:54 +0200 [thread overview]
Message-ID: <1c570243-45b2-4813-b070-9b22dfa787eb@oss.qualcomm.com> (raw)
In-Reply-To: <ec4d11b5-7a82-4e7f-bab6-290d1055f1d8@oldschoolsolutions.biz>
On 5/20/26 9:45 AM, Jens Glathe wrote:
> On 18.05.26 14:08, Pengyu Luo wrote:
>> I think they might take the power sequence into account when they were
>> introducing the devices, vdda-phy(~0.9v) first and vdda-pll(1.2v)
>> later in the upstream while vdd(0.912v) first and core(1.2v) later in
>> the downstream. BTW, the DSDT is unreliable. On my platform, it
>> describes that several components are consuming several LDOs, but
>> these components work well with these LDOs manually disabled via rpmh.
>>
>> Best wishes,
>> Pengyu
>>
> Hmm looks like schematics would trump these speculations. Maybe wait until this can be confirmed.
My previous reply was wrong.
via CRD8280X schematics:
USB0 USB1 USB2 USB3 USB4 USB5
HSPHY 0p9 L9D L4B L1B L8D [L10D L10D]
HSPHY 1p8 L1C L1C [L1C L1C] [L8C L8C]
HSPHY 3p1 L7D L13C [L7D L7D] [L2D L2D]
SSPHY 0p9 L9D L4B L1B L8D N/A N/A
SSPHY 1p2 L4D L3B L4D L4D N/A N/A
USB0 - usb@a600000
USB1 - usb@a800000
USB2/3 - usb@a400000 ports 0/1
USB4/5 - usb@a400000 ports 2/3
Regulators in square brackets share a single input pin on the SoC
Konrad
prev parent reply other threads:[~2026-05-21 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 9:23 Pengyu Luo
2025-01-10 12:28 ` Konrad Dybcio
2025-01-10 14:25 ` Pengyu Luo
2026-05-16 19:19 ` Jens Glathe
2026-05-18 12:08 ` Pengyu Luo
2026-05-20 7:45 ` Jens Glathe
2026-05-21 9:25 ` Konrad Dybcio [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=1c570243-45b2-4813-b070-9b22dfa787eb@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.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=mitltlatltl@gmail.com \
--cc=robh@kernel.org \
--cc=sophon@radxa.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®