From: Wei Deng <wei.deng@oss.qualcomm.com>
To: 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, linux-bluetooth@vger.kernel.org,
cheng.jiang@oss.qualcomm.com, quic_jiaymao@quicinc.com,
quic_chezhou@quicinc.com, quic_shuaz@quicinc.com
Subject: [PATCH] arm64: dts: qcom: qcs8300-ride: Enable Bluetooth support
Date: Thu, 13 Nov 2025 18:39:42 +0530 [thread overview]
Message-ID: <20251113130942.2661069-1-wei.deng@oss.qualcomm.com> (raw)
Enable BT on qcs8300-ride by adding a device tree node for BT.
Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com>
---
This patch depends on:
- WLAN
https://lore.kernel.org/all/20251113055148.2729943-1-wei.zhang@oss.qualcomm.com/
---
arch/arm64/boot/dts/qcom/qcs8300-ride.dts | 28 +++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/qcs8300-ride.dts b/arch/arm64/boot/dts/qcom/qcs8300-ride.dts
index cd8800a59700..08b705fe4eea 100644
--- a/arch/arm64/boot/dts/qcom/qcs8300-ride.dts
+++ b/arch/arm64/boot/dts/qcom/qcs8300-ride.dts
@@ -18,6 +18,7 @@ / {
aliases {
serial0 = &uart7;
mmc0 = &sdhc_1;
+ serial1 = &uart2;
};
chosen {
@@ -71,6 +72,7 @@ wcn6855-pmu {
vddpcie1p3-supply = <&vreg_conn_pa>;
vddpcie1p9-supply = <&vreg_conn_1p8>;
+ bt-enable-gpios = <&tlmm 55 GPIO_ACTIVE_HIGH>;
wlan-enable-gpios = <&tlmm 54 GPIO_ACTIVE_HIGH>;
regulators {
@@ -501,6 +503,13 @@ &sdhc_1 {
};
&tlmm {
+ bt_en_state: bt-en-state {
+ pins = "gpio55";
+ function = "gpio";
+ bias-pull-down;
+ output-low;
+ };
+
ethernet0_default: ethernet0-default-state {
ethernet0_mdc: ethernet0-mdc-pins {
pins = "gpio5";
@@ -571,6 +580,25 @@ wlan_en_state: wlan-en-state {
};
};
+&uart2 {
+ status = "okay";
+
+ bluetooth: bluetooth {
+ compatible = "qcom,wcn6855-bt";
+ firmware-name = "QCA6698/hpnv21", "QCA6698/hpbtfw21.tlv";
+ max-speed = <3200000>;
+
+ vddrfacmn-supply = <&vreg_pmu_rfa_cmn>;
+ vddaon-supply = <&vreg_pmu_aon_0p59>;
+ vddwlcx-supply = <&vreg_pmu_wlcx_0p8>;
+ vddwlmx-supply = <&vreg_pmu_wlmx_0p85>;
+ vddbtcmx-supply = <&vreg_pmu_btcmx_0p85>;
+ vddrfa0p8-supply = <&vreg_pmu_rfa_0p8>;
+ vddrfa1p2-supply = <&vreg_pmu_rfa_1p2>;
+ vddrfa1p8-supply = <&vreg_pmu_rfa_1p7>;
+ };
+};
+
&uart7 {
status = "okay";
};
--
2.25.1
next reply other threads:[~2025-11-13 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 13:09 Wei Deng [this message]
2025-11-13 13:37 ` [PATCH] arm64: dts: qcom: qcs8300-ride: Enable Bluetooth support Krzysztof Kozlowski
2025-11-13 13:38 ` Krzysztof Kozlowski
2025-11-18 13:18 ` Wei Deng
2025-11-13 20:14 ` Dmitry Baryshkov
2025-11-14 9:40 ` Wei Deng
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=20251113130942.2661069-1-wei.deng@oss.qualcomm.com \
--to=wei.deng@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--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-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_chezhou@quicinc.com \
--cc=quic_jiaymao@quicinc.com \
--cc=quic_shuaz@quicinc.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