From: Johan Hovold <johan@kernel.org>
To: Stephan Gerhold <stephan.gerhold@linaro.org>
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>,
Abel Vesa <abel.vesa@linaro.org>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
Marc Zyngier <maz@kernel.org>, Xilin Wu <wuxilin123@gmail.com>,
Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
Srinivas Kandagatla <srini@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] arm64: dts: qcom: x1*: Fix vreg_l2j_1p2 voltage
Date: Tue, 29 Apr 2025 15:02:37 +0200 [thread overview]
Message-ID: <aBDN7V6eFoIn6r0J@hovoldconsulting.com> (raw)
In-Reply-To: <20250423-x1e-vreg-l2j-voltage-v1-0-24b6a2043025@linaro.org>
On Wed, Apr 23, 2025 at 09:30:06AM +0200, Stephan Gerhold wrote:
> Several of the Qualcomm X1* device trees upstream specify the wrong voltage
> for the L2J regulator. In the ACPI DSDT table, PPP_RESOURCE_ID_LDO2_J is
> configured with 1256000 uV instead of the 1200000 uV. Change all affected
> device trees to use the same for consistency and correctness.
>
> In the other device trees upstream, the voltage is already correct:
> - x1e78100-lenovo-thinkpad-t14s.dtsi
> - x1e80100-dell-xps13-9345.dts
> - x1e80100-microsoft-romulus.dtsi
>
> Signed-off-by: Stephan Gerhold <stephan.gerhold@linaro.org>
> ---
> Stephan Gerhold (6):
> arm64: dts: qcom: x1-crd: Fix vreg_l2j_1p2 voltage
> arm64: dts: qcom: x1e001de-devkit: Fix vreg_l2j_1p2 voltage
> arm64: dts: qcom: x1e80100-asus-vivobook-s15: Fix vreg_l2j_1p2 voltage
> arm64: dts: qcom: x1e80100-hp-omnibook-x14: Fix vreg_l2j_1p2 voltage
> arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Fix vreg_l2j_1p2 voltage
> arm64: dts: qcom: x1e80100-qcp: Fix vreg_l2j_1p2 voltage
I only checked the CRD (and T14s) DSDT, but this looks correct:
Reviewed-by: Johan Hovold <johan+linaro@kernel.org>
next prev parent reply other threads:[~2025-04-29 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 7:30 [PATCH 0/6] arm64: dts: qcom: x1*: Fix vreg_l2j_1p2 voltage Stephan Gerhold
2025-04-23 7:30 ` [PATCH 1/6] arm64: dts: qcom: x1-crd: " Stephan Gerhold
2025-04-23 7:30 ` [PATCH 2/6] arm64: dts: qcom: x1e001de-devkit: " Stephan Gerhold
2025-04-23 7:30 ` [PATCH 3/6] arm64: dts: qcom: x1e80100-asus-vivobook-s15: " Stephan Gerhold
2025-04-23 7:30 ` [PATCH 4/6] arm64: dts: qcom: x1e80100-hp-omnibook-x14: " Stephan Gerhold
2025-04-23 7:30 ` [PATCH 5/6] arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: " Stephan Gerhold
2025-04-23 7:30 ` [PATCH 6/6] arm64: dts: qcom: x1e80100-qcp: " Stephan Gerhold
2025-04-23 9:17 ` [PATCH 0/6] arm64: dts: qcom: x1*: " Konrad Dybcio
2025-04-24 6:49 ` Abel Vesa
2025-04-29 13:02 ` Johan Hovold [this message]
2025-05-07 5:18 ` 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=aBDN7V6eFoIn6r0J@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--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=maz@kernel.org \
--cc=quic_rjendra@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=stephan.gerhold@linaro.org \
--cc=wuxilin123@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.