From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: david@ixit.cz, 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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH] testing! arm64: dts: qcom: decrease WiFi antenna regulator minimum to 3.0V
Date: Thu, 5 Feb 2026 10:05:13 +0100 [thread overview]
Message-ID: <d800d5cc-0e57-401a-a62a-42e9c40125f6@oss.qualcomm.com> (raw)
In-Reply-To: <20260204-oneplus6-wifi-voltage-v1-1-ee6fd47f9d02@ixit.cz>
On 2/4/26 6:03 PM, David Heidelberg via B4 Relay wrote:
> From: David Heidelberg <david@ixit.cz>
>
> Downstream defines minimal voltage as 3.0 V, while when OnePlus 6 was
> introduced to Linux mainline, the value was fixed to maximum 3.3V.
>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> Tested for ~ 1 month. Seems to work well, no visible issues anywhere.
> ---
> arch/arm64/boot/dts/qcom/sdm845-oneplus-common.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-oneplus-common.dtsi b/arch/arm64/boot/dts/qcom/sdm845-oneplus-common.dtsi
> index 5b121ea5520f5..e950db41ce25a 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845-oneplus-common.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm845-oneplus-common.dtsi
> @@ -307,7 +307,7 @@ vreg_l20a_2p95: ldo20 {
> };
>
> vreg_l23a_3p3: ldo23 {
> - regulator-min-microvolt = <3300000>;
> + regulator-min-microvolt = <3000000>;
> regulator-max-microvolt = <3312000>;
> regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> };
> @@ -320,7 +320,7 @@ vreg_l24a_3p075: ldo24 {
> };
>
> vreg_l25a_3p3: ldo25 {
> - regulator-min-microvolt = <3300000>;
> + regulator-min-microvolt = <3000000>;
> regulator-max-microvolt = <3312000>;
A datasheet tells me this is out of spec for this wireless chip
Konrad
next prev parent reply other threads:[~2026-02-05 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 17:03 David Heidelberg via B4 Relay
2026-02-05 9:05 ` Konrad Dybcio [this message]
2026-02-05 9:58 ` David Heidelberg
2026-02-05 10:51 ` Konrad Dybcio
2026-02-05 11:46 ` David Heidelberg
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=d800d5cc-0e57-401a-a62a-42e9c40125f6@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--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=phone-devel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®