From: Bjorn Andersson <andersson@kernel.org>
To: Qian Zhang <qian.zhang@oss.qualcomm.com>
Cc: konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64: dts: qcom: Add fixed regulators for WLAN supplies
Date: Thu, 7 May 2026 08:58:01 -0500 [thread overview]
Message-ID: <afyYaCSFXy-Fm7DR@baldur> (raw)
In-Reply-To: <20260501051918.1990713-1-qian.zhang@oss.qualcomm.com>
On Fri, May 01, 2026 at 01:19:18PM +0800, Qian Zhang wrote:
There shouldn't be a "v1" tag in your subject, and the subject prefix
should be:
arm64: dts: qcom: monaco-arduino-monza: ...
> Add GPIO-controlled fixed regulators for the WLAN power rails on the
> Arduino VENTUNO Q board:
>
> - wlan_reg_3v3: 3.3V supply controlled by GPIO54 (wlan_rf_kill)
> - wlan_reg_1v8: 1.8V supply controlled by GPIO56 (wlan_en)
Those really sounds like gpios, rather than regulators. Why are they
represented as regulators. Please start your commit message by
describing the "problem" that you're solving.
>
> Both regulators are enabled at boot to support WLAN initialization.
>
> Signed-off-by: Qian Zhang <qian.zhang@oss.qualcomm.com>
> ---
> Changes in v1:
What do you mean? Changes since version 0?
> - Clarified GPIO roles: GPIO54 for wlan_rf_kill, GPIO56 for wlan_en
> - Improved commit message readability with bullet list format
It's impossible for me to know if the regulator vs gpio was already
discussed, because you didn't include a link to the previous version.
Use b4 instead of doing your own thing, it will handle the versioning
for you and it will provide links to previous versions.
>
> .../boot/dts/qcom/monaco-arduino-monza.dts | 21 +++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/monaco-arduino-monza.dts b/arch/arm64/boot/dts/qcom/monaco-arduino-monza.dts
> index ca14f0ea4dae..1a40ac5bb4bb 100644
> --- a/arch/arm64/boot/dts/qcom/monaco-arduino-monza.dts
> +++ b/arch/arm64/boot/dts/qcom/monaco-arduino-monza.dts
> @@ -153,6 +153,27 @@ vreg_nvme: regulator-3p3-m2 {
> enable-active-high;
> startup-delay-us = <20000>;
> };
> +
> + wlan_reg_3v3: wlan-3v3-regulator {
> + compatible = "regulator-fixed";
> + regulator-name = "wlan_3v3";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + gpio = <&tlmm 54 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> + regulator-boot-on;
> + };
> +
> + wlan_reg_1v8: wlan-1v8-regulator {
Shouldn't these two regulators be referenced from a WiFi or PMU node?
Regards,
Bjorn
> + compatible = "regulator-fixed";
> + regulator-name = "wlan_1v8";
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> + gpio = <&tlmm 56 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> + regulator-boot-on;
> + };
> +
> };
>
> ðernet0 {
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-05-07 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260501051918.1990713-1-qian.zhang@oss.qualcomm.com>
2026-05-07 13:42 ` [PATCH v1] arm64: dts: qcom: Add fixed regulators for WLAN supplies Shawn Guo
2026-05-07 13:58 ` Bjorn Andersson [this message]
2026-05-09 3:15 ` Qian Zhang
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=afyYaCSFXy-Fm7DR@baldur \
--to=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=qian.zhang@oss.qualcomm.com \
--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