From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "Yu Zhang(Yuriy)" <quic_yuzha@quicinc.com>,
andersson@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: agross@kernel.org, ath11k@lists.infradead.org,
dmitry.baryshkov@linaro.org, konradybcio@kernel.org,
kvalo@kernel.org, linux-media@vger.kernel.org,
mchehab@kernel.org, quic_jjohnson@quicinc.com,
quic_miaoqing@quicinc.com, quic_vgarodia@quicinc.com,
stanimir.k.varbanov@gmail.com, quic_jiaymao@quicinc.com
Subject: Re: [PATCH v3] arm64: dts: qcom: qcs615: add WiFi/BT nodes
Date: Thu, 5 Dec 2024 18:14:48 +0100 [thread overview]
Message-ID: <1ca062dd-8910-4caf-a133-0e5717b43540@oss.qualcomm.com> (raw)
In-Reply-To: <20241203060318.1750927-1-quic_yuzha@quicinc.com>
On 3.12.2024 7:03 AM, Yu Zhang(Yuriy) wrote:
> Add a node for the PMU module of the WCN6855 present on the qcs615
> board. Assign its LDO power outputs to the existing WiFi/BT module.
>
subject:
arm64: dts: qcom: qcs615-ride: ....
[...]
> +
> + vreg_conn_1p8: vreg_conn_1p8 {
> + compatible = "regulator-fixed";
> + regulator-name = "vreg_conn_1p8";
> + startup-delay-us = <4000>;
> + enable-active-high;
> + gpio = <&pm8150_gpios 1 GPIO_ACTIVE_HIGH>;
> + };
> +
> + vreg_conn_pa: vreg_conn_pa {
> + compatible = "regulator-fixed";
> + regulator-name = "vreg_conn_pa";
> + startup-delay-us = <4000>;
> + enable-active-high;
> + gpio = <&pm8150_gpios 6 GPIO_ACTIVE_HIGH>;
> + };
Are any of these boot-on?
> +
> + wcn6855-pmu {
> + compatible = "qcom,wcn6855-pmu";
> +
> + pinctrl-0 = <&bt_en_state>, <&wlan_en_state>;
> + pinctrl-names = "default";
> +
> + vddio-supply = <&vreg_conn_pa>;
> + vddaon-supply = <&vreg_s5a>;
> + vddpmu-supply = <&vreg_conn_1p8>;
> + vddrfa0p95-supply = <&vreg_s5a>;
> + vddrfa1p3-supply = <&vreg_s6a>;
> + vddrfa1p9-supply = <&vreg_l15a>;
> + vddpcie1p3-supply = <&vreg_s6a>;
> + vddpcie1p9-supply = <&vreg_l15a>;
> +
> + bt-enable-gpios = <&tlmm 85 GPIO_ACTIVE_HIGH>;
> + wlan-enable-gpios = <&tlmm 98 GPIO_ACTIVE_HIGH>;
Please move these properties above supplies, to match the style in
other recent device trees
[...]
> &rpmhcc {
> clocks = <&xo_board_clk>;
> };
> @@ -262,12 +363,42 @@ wake-pins {
> bias-pull-up;
> };
> };
> +
> + wlan_en_state: wlan-en-state {
> + pins = "gpio98";
> + function = "gpio";
> + drive-strength = <16>;
> + output-high;
> + bias-pull-up;
> + };
> +
> + bt_en_state: bt-en-state {
> + pins = "gpio85";
> + function = "gpio";
> + output-low;
> + bias-pull-down;
> + };
These should be sorted by gpio idx
Konrad
next prev parent reply other threads:[~2024-12-05 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 6:03 [PATCH v3] arm64: dts: qcom: qcs615: add WiFi/BT nodes Yu Zhang(Yuriy)
2024-12-03 13:08 ` Dmitry Baryshkov
2024-12-05 17:14 ` Konrad Dybcio [this message]
2024-12-06 3:22 ` Yu Zhang (Yuriy)
2024-12-06 12:16 ` Konrad Dybcio
2024-12-10 2:37 ` Yu Zhang (Yuriy)
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=1ca062dd-8910-4caf-a133-0e5717b43540@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_jiaymao@quicinc.com \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_miaoqing@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=quic_yuzha@quicinc.com \
--cc=stanimir.k.varbanov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox