From: Harish Bandi <c-hbandi@codeaurora.org>
To: marcel@holtmann.org, johan.hedberg@gmail.com
Cc: mka@chromium.org, linux-kernel@vger.kernel.org,
linux-bluetooth@vger.kernel.org, hemantg@codeaurora.org,
linux-arm-msm@vger.kernel.org, bgodavar@codeaurora.org,
anubhavg@codeaurora.org, devicetree@vger.kernel.org,
mark.rutland@arm.com, robh+dt@kernel.org,
Harish Bandi <c-hbandi@codeaurora.org>
Subject: [PATCH v6 2/2] dt-bindings: net: bluetooth: Add device tree bindings for QTI chip WCN3998
Date: Wed, 27 Mar 2019 17:58:43 +0530 [thread overview]
Message-ID: <1553689723-21017-3-git-send-email-c-hbandi@codeaurora.org> (raw)
In-Reply-To: <1553689723-21017-1-git-send-email-c-hbandi@codeaurora.org>
This patch enables regulators for the Qualcomm Bluetooth WCN3998
controller.
Signed-off-by: Harish Bandi <c-hbandi@codeaurora.org>
---
Changes in V6:
- no changes
---
Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
index 824c0e2..7ef6118 100644
--- a/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
+++ b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
@@ -11,20 +11,21 @@ Required properties:
- compatible: should contain one of the following:
* "qcom,qca6174-bt"
* "qcom,wcn3990-bt"
+ * "qcom,wcn3998-bt"
Optional properties for compatible string qcom,qca6174-bt:
- enable-gpios: gpio specifier used to enable chip
- clocks: clock provided to the controller (SUSCLK_32KHZ)
-Required properties for compatible string qcom,wcn3990-bt:
+Required properties for compatible string qcom,wcn399x-bt:
- vddio-supply: VDD_IO supply regulator handle.
- vddxo-supply: VDD_XO supply regulator handle.
- vddrf-supply: VDD_RF supply regulator handle.
- vddch0-supply: VDD_CH0 supply regulator handle.
-Optional properties for compatible string qcom,wcn3990-bt:
+Optional properties for compatible string qcom,wcn399x-bt:
- max-speed: see Documentation/devicetree/bindings/serial/slave-device.txt
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2019-03-27 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 12:28 [PATCH v6 0/2] Enable Bluetooth functionality for WCN3998 Harish Bandi
2019-03-27 12:28 ` [PATCH v6 1/2] Bluetooth: hci_qca: Added support " Harish Bandi
2019-03-27 16:46 ` Balakrishna Godavarthi
2019-03-27 16:56 ` Matthias Kaehlcke
2019-03-29 4:40 ` Harish Bandi
2019-03-28 21:05 ` kbuild test robot
2019-03-28 21:23 ` Matthias Kaehlcke
2019-03-29 4:42 ` Harish Bandi
2019-03-27 12:28 ` Harish Bandi [this message]
2019-03-27 17:29 ` [PATCH v6 2/2] dt-bindings: net: bluetooth: Add device tree bindings for QTI chip WCN3998 Matthias Kaehlcke
2019-03-29 4:38 ` Harish Bandi
2019-04-01 12:39 ` Harish Bandi
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=1553689723-21017-3-git-send-email-c-hbandi@codeaurora.org \
--to=c-hbandi@codeaurora.org \
--cc=anubhavg@codeaurora.org \
--cc=bgodavar@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=hemantg@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).