From: Johan Hovold <johan+linaro@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sibi Sankar <quic_sibis@quicinc.com>,
Abel Vesa <abel.vesa@linaro.org>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>,
stable@vger.kernel.org
Subject: [PATCH 1/7] arm64: dts: qcom: x1e80100-crd: fix PCIe4 PHY supply
Date: Fri, 19 Jul 2024 15:17:16 +0200 [thread overview]
Message-ID: <20240719131722.8343-2-johan+linaro@kernel.org> (raw)
In-Reply-To: <20240719131722.8343-1-johan+linaro@kernel.org>
The PCIe4 PHY is powered by vreg_l3i (not vreg_l3j).
Fixes: d7e03cce0400 ("arm64: dts: qcom: x1e80100-crd: Enable more support")
Cc: stable@vger.kernel.org # 6.9
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
---
arch/arm64/boot/dts/qcom/x1e80100-crd.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/x1e80100-crd.dts b/arch/arm64/boot/dts/qcom/x1e80100-crd.dts
index f97c80b4077c..6aa2ec1e7919 100644
--- a/arch/arm64/boot/dts/qcom/x1e80100-crd.dts
+++ b/arch/arm64/boot/dts/qcom/x1e80100-crd.dts
@@ -788,7 +788,7 @@ &pcie4 {
};
&pcie4_phy {
- vdda-phy-supply = <&vreg_l3j_0p8>;
+ vdda-phy-supply = <&vreg_l3i_0p8>;
vdda-pll-supply = <&vreg_l3e_1p2>;
status = "okay";
--
2.44.2
next prev parent reply other threads:[~2024-07-19 13:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 13:17 [PATCH 0/7] arm64: dts: qcom: x1e80100: PCIe fixes and CRD modem support Johan Hovold
2024-07-19 13:17 ` Johan Hovold [this message]
2024-07-19 18:34 ` [PATCH 1/7] arm64: dts: qcom: x1e80100-crd: fix PCIe4 PHY supply Konrad Dybcio
2024-07-22 7:34 ` Johan Hovold
2024-07-19 13:17 ` [PATCH 2/7] arm64: dts: qcom: x1e80100: fix PCIe domain numbers Johan Hovold
2024-07-19 18:42 ` Konrad Dybcio
2024-07-19 13:17 ` [PATCH 3/7] arm64: dts: qcom: x1e80100-crd: fix up PCIe6a pinctrl node Johan Hovold
2024-07-19 18:35 ` Konrad Dybcio
2024-07-19 13:17 ` [PATCH 4/7] arm64: dts: qcom: x1e80100-crd: disable PCIe6a perst pull down Johan Hovold
2024-07-19 18:42 ` Konrad Dybcio
2024-07-19 13:17 ` [PATCH 5/7] arm64: dts: qcom: x1e80100-crd: fix missing PCIe4 gpios Johan Hovold
2024-07-19 18:36 ` Konrad Dybcio
2024-07-22 7:38 ` Johan Hovold
2024-07-19 13:17 ` [PATCH 6/7] arm64: dts: qcom: x1e80100: add PCIe5 nodes Johan Hovold
2024-07-19 18:39 ` Konrad Dybcio
2024-07-22 7:40 ` Johan Hovold
2024-07-19 13:17 ` [PATCH 7/7] arm64: dts: qcom: x1e80100-crd: enable SDX65 modem Johan Hovold
2024-07-19 18:43 ` Konrad Dybcio
2024-07-23 2:57 ` [PATCH 0/7] arm64: dts: qcom: x1e80100: PCIe fixes and CRD modem support Rob Herring (Arm)
2024-07-23 15:24 ` Johan Hovold
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=20240719131722.8343-2-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_rjendra@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=robh@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).