linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Balakrishna Godavarthi <bgodavar@codeaurora.org>
To: marcel@holtmann.org, johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org, rtatiya@codeaurora.org,
	linux-arm-msm@vger.kernel.org
Subject: [PATCH 1/3] Bluetooth: Add device tree bindings for Atheros chips
Date: Fri,  6 Apr 2018 17:22:24 +0530	[thread overview]
Message-ID: <1523015546-994-2-git-send-email-bgodavar@codeaurora.org> (raw)
In-Reply-To: <1523015546-994-1-git-send-email-bgodavar@codeaurora.org>

From: Rupesh Tatiya <rtatiya@codeaurora.org>

Change-Id: Ie62e3b90b6226019142206c8d44712a6c8550ef2
Signed-off-by: Rupesh Tatiya <rtatiya@codeaurora.org>
---
 .../devicetree/bindings/bluetooth/btqca_power.txt  | 30 ++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/bluetooth/btqca_power.txt

diff --git a/Documentation/devicetree/bindings/bluetooth/btqca_power.txt b/Documentation/devicetree/bindings/bluetooth/btqca_power.txt
new file mode 100644
index 0000000..f0f593c
--- /dev/null
+++ b/Documentation/devicetree/bindings/bluetooth/btqca_power.txt
@@ -0,0 +1,30 @@
+* Bluetooth Controller
+Bluetooth controller communicates with the Bluetooth Host using HCI Transport layer.
+HCI Transport layer can be based on UART or USB serial communication protocol.
+
+Required properties:
+  - compatible: Should be set to one of the following:
+	qca,ar3002
+	qca,qca6174
+	qca,wcn3990
+
+Optional properties:
+  - vddpa-supply: Bluetooth VDD PA regulator handle
+  - vddio-supply: Bluetooth VDD IO regulator handle
+  - vddldo-supply: Bluetooth VDD LDO regulator handle. Kept under optional parameters
+		as some of the chipsets doesn't require ldo or it may use from same vddio.
+  - vddxtal-supply: Bluetooth VDD XTAL regulator handle
+  - vddcore-supply: Bluetooth VDD CORE regulator handle
+  - vddpwd-supply: Chip power down gpio is required when bluetooth module
+		and other modules like wifi co-exist in a singe chip and shares a
+		common gpio to bring chip out of reset.
+
+Example:
+  bt-ar3002 {
+    compatible = "qca,ar3002";
+    vddio-supply = <&pm8941_s3>;
+    vddpa-supply = <&pm8941_l19>;
+    vddxtal-supply = <&pm8994_l30>;
+    vddcore-supply = <&pm8994_s3>;
+    vddpwd-supply = <&ath_chip_pwd_l>;
+};
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2018-04-06 11:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 11:52 [PATCH 0/3] Enable Bluetooth functionality for WCN3990 Balakrishna Godavarthi
2018-04-06 11:52 ` Balakrishna Godavarthi [this message]
2018-04-06 16:49   ` [PATCH 1/3] Bluetooth: Add device tree bindings for Atheros chips Marcel Holtmann
2018-04-06 11:52 ` [PATCH 2/3] Add support to power Bluetooth QCA chips attached to MSM Balakrishna Godavarthi
2018-04-06 16:47   ` Marcel Holtmann
2018-04-12 13:23     ` rtatiya
2018-04-12 14:52       ` Marcel Holtmann
2018-04-06 11:52 ` [PATCH 3/3] Bluetooth: Added support for wcn3990 soc Balakrishna Godavarthi

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=1523015546-994-2-git-send-email-bgodavar@codeaurora.org \
    --to=bgodavar@codeaurora.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=rtatiya@codeaurora.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).