From: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Georgi Djakov <djakov@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
Yepuri Siddu <yepuri.siddu@oss.qualcomm.com>,
Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
Subject: Re: [PATCH v5 10/11] arm64: dts: qcom: shikra: Enable Bluetooth and WiFi on EVK boards
Date: Tue, 7 Jul 2026 19:13:42 +0530 [thread overview]
Message-ID: <1bbe5560-3a65-41d0-8aec-4d07bc8d05bd@oss.qualcomm.com> (raw)
In-Reply-To: <zjvb6i3rahc2kwojxrg4cwaqtddcho2nj3sfcr63xkkrm7tdd2@2yl6rxb7rtcb>
On 7/2/2026 5:26 PM, Dmitry Baryshkov wrote:
> On Thu, Jul 02, 2026 at 03:20:52PM +0530, Komal Bajaj wrote:
>> Enable Bluetooth and WiFi connectivity on Shikra CQM, CQS and IQS
>> EVK boards using the WCN3988 combo chip.
>>
>> For Bluetooth, enable uart8 and add WCN3988 Bluetooth node with
>> board-specific regulator supplies across CQM, CQS and IQS Shikra
>> EVK boards.
>>
>> For WiFi, enable per-board with the appropriate PMIC supply
>> connections and calibration variant selection.
> This is obvious from the patch itself. Don't repeat patch contents, say
> something useful.
ACK, will update commit message.
>
>> Co-developed-by: Yepuri Siddu <yepuri.siddu@oss.qualcomm.com>
>> Signed-off-by: Yepuri Siddu <yepuri.siddu@oss.qualcomm.com>
>> Co-developed-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
>> Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>> Signed-off-by: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts | 18 +++++++++
>> arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts | 18 +++++++++
>> arch/arm64/boot/dts/qcom/shikra-evk.dtsi | 61 +++++++++++++++++++++++++++++
>> arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts | 26 ++++++++++++
>> 4 files changed, 123 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts b/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
>> index b112b21b1d79..c9409ab0a3f1 100644
>> --- a/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
>> +++ b/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
>> @@ -16,11 +16,19 @@ / {
>> aliases {
>> mmc0 = &sdhc_1;
>> serial0 = &uart0;
>> + serial1 = &uart8;
>> };
>>
>> chosen {
>> stdout-path = "serial0:115200n8";
>> };
>> +
>> + wcn3988-pmu {
>> + vddio-supply = <&pm4125_l7>;
>> + vddxo-supply = <&pm4125_l13>;
>> + vddrf-supply = <&pm4125_l10>;
>> + vddch0-supply = <&pm4125_l22>;
>> + };
> Is the WiFI/BT chip a part of common schematics or not? Why do you
> define power supplies here, while the chip itself is defined in a common
> file?
You're right. WCN3988 is integrated on SoM, and its regulator
dependencies are provided by SoM PMIC.
I'll move the supply definitions to SoM DTSI.
>
>> };
>>
>> &remoteproc_cdsp {
>> @@ -57,3 +65,13 @@ &sdhc_1 {
>>
>> status = "okay";
>> };
>> +
>> +&uart8 {
>> + status = "okay";
>> +};
> Same question.
I'll move to SoM DTSI.
Thanks
Komal
>
>> +
>> +&wifi {
>> + vdd-0.8-cx-mx-supply = <&pm4125_l7>;
>> +
>> + status = "okay";
>> +};
>> diff --git a/arch/arm64/boot/dts/qcom/shikra-evk.dtsi b/arch/arm64/boot/dts/qcom/shikra-evk.dtsi
>> index d0c48bad704c..4b7be09eb5a5 100644
>> --- a/arch/arm64/boot/dts/qcom/shikra-evk.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/shikra-evk.dtsi
>> @@ -3,13 +3,74 @@
>> * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
>> */
>>
>> +/ {
>> + wcn3988-pmu {
>> + compatible = "qcom,wcn3988-pmu";
>> +
>> + pinctrl-0 = <&sw_ctrl_default>;
>> + pinctrl-names = "default";
>> +
>> + swctrl-gpios = <&tlmm 88 GPIO_ACTIVE_HIGH>;
>> +
>> + regulators {
>> + vreg_pmu_io: ldo0 {
>> + regulator-name = "vreg_pmu_io";
>> + };
>> +
>> + vreg_pmu_xo: ldo1 {
>> + regulator-name = "vreg_pmu_xo";
>> + };
>> +
>> + vreg_pmu_rf: ldo2 {
>> + regulator-name = "vreg_pmu_rf";
>> + };
>> +
>> + vreg_pmu_ch0: ldo3 {
>> + regulator-name = "vreg_pmu_ch0";
>> + };
>> +
>> + vreg_pmu_ch1: ldo4 {
>> + regulator-name = "vreg_pmu_ch1";
>> + };
>> + };
>> + };
>> +};
>> +
>> &qupv3_0 {
>> firmware-name = "qcom/shikra/qupv3fw.elf";
>>
>> status = "okay";
>> };
>>
>> +&tlmm {
>> + sw_ctrl_default: sw-ctrl-default-state {
>> + pins = "gpio88";
>> + function = "gpio";
>> + bias-pull-down;
>> + };
>> +};
>> +
>> &uart0 {
>> status = "okay";
>> };
>>
>> +&uart8 {
>> + bluetooth {
>> + compatible = "qcom,wcn3988-bt";
>> + max-speed = <3200000>;
>> +
>> + vddio-supply = <&vreg_pmu_io>;
>> + vddxo-supply = <&vreg_pmu_xo>;
>> + vddrf-supply = <&vreg_pmu_rf>;
>> + vddch0-supply = <&vreg_pmu_ch0>;
>> + };
>> +};
>> +
>> +&wifi {
>> + vdd-1.8-xo-supply = <&vreg_pmu_xo>;
>> + vdd-1.3-rfa-supply = <&vreg_pmu_rf>;
>> + vdd-3.3-ch0-supply = <&vreg_pmu_ch0>;
>> +
>> + qcom,calibration-variant = "Shikra_EVK";
>> + firmware-name = "shikra";
>> +};
next prev parent reply other threads:[~2026-07-07 13:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:50 [PATCH v5 00/11] arm64: dts: qcom: Extend Shikra device tree with peripheral and subsystem support Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 01/11] dt-bindings: interconnect: qcom-bwmon: Add Shikra cpu-bwmon compatible Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 02/11] arm64: dts: qcom: Add QUPv3 configuration for Shikra Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 03/11] arm64: dts: qcom: shikra: Add DDR BWMON support Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 04/11] arm64: dts: qcom: shikra: Add cpufreq-hw, EPSS L3 interconnect and OPP tables Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 05/11] arm64: dts: qcom: shikra: Add SMP2P nodes Komal Bajaj
2026-07-02 10:56 ` Konrad Dybcio
2026-07-02 9:50 ` [PATCH v5 06/11] arm64: dts: qcom: shikra: Add CDSP, LPAICP, MPSS remoteproc PAS nodes Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 07/11] arm64: dts: qcom: shikra: Enable CDSP, LPAICP and MPSS on EVK boards Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 08/11] arm64: dts: qcom: shikra: Enable TSENS and thermal zones Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 09/11] arm64: dts: qcom: shikra: add WiFi node support Komal Bajaj
2026-07-02 10:57 ` Konrad Dybcio
2026-07-02 9:50 ` [PATCH v5 10/11] arm64: dts: qcom: shikra: Enable Bluetooth and WiFi on EVK boards Komal Bajaj
2026-07-02 10:59 ` Konrad Dybcio
2026-07-07 13:43 ` Komal Bajaj
2026-07-02 11:56 ` Dmitry Baryshkov
2026-07-07 13:43 ` Komal Bajaj [this message]
2026-07-02 9:50 ` [PATCH v5 11/11] arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm Komal Bajaj
2026-07-02 10:55 ` Konrad Dybcio
2026-07-07 16:36 ` Komal Bajaj
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=1bbe5560-3a65-41d0-8aec-4d07bc8d05bd@oss.qualcomm.com \
--to=komal.bajaj@oss.qualcomm.com \
--cc=Frank.Li@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=miaoqing.pan@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
--cc=yepuri.siddu@oss.qualcomm.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