From: Balakrishna Godavarthi <bgodavar@codeaurora.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-bluetooth@vger.kernel.org, thierry.escande@linaro.org,
rtatiya@codeaurora.org, hemantg@codeaurora.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v12 1/7] dt-bindings: net: bluetooth: Add device tree bindings for QTI chip wcn3990
Date: Thu, 02 Aug 2018 23:35:54 +0530 [thread overview]
Message-ID: <58791a55af5532d476febddea6756fdb@codeaurora.org> (raw)
In-Reply-To: <366e23679cabb332b1ecde8396570f66@codeaurora.org>
Hi Matthias,
On 2018-08-02 23:24, Balakrishna Godavarthi wrote:
> Hi Matthias,
>
> On 2018-08-02 22:50, Matthias Kaehlcke wrote:
>> On Thu, Aug 02, 2018 at 06:55:12PM +0530, Balakrishna Godavarthi
>> wrote:
>>> This patch enables regulators for the Qualcomm Bluetooth wcn3990
>>> controller.
>>>
>>> Signed-off-by: Balakrishna Godavarthi <bgodavar@codeaurora.org>
>>> Reviewed-by: Rob Herring <robh@kernel.org>
>>> ---
>>> .../bindings/net/qualcomm-bluetooth.txt | 26
>>> +++++++++++++++++--
>>> 1 file changed, 24 insertions(+), 2 deletions(-)
>>>
>>> diff --git
>>> a/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
>>> b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
>>> index 0ea18a53cc29..2175174415ee 100644
>>> --- a/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
>>> +++ b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
>>> @@ -10,12 +10,22 @@ device the slave device is attached to.
>>> Required properties:
>>> - compatible: should contain one of the following:
>>> * "qcom,qca6174-bt"
>>> + * "qcom,wcn3990-bt"
>>> +
>>> +Optional properties for compatible string qcom,qca6174-bt:
>>>
>>> -Optional properties:
>>> - enable-gpios: gpio specifier used to enable chip
>>> - clocks: clock provided to the controller (SUSCLK_32KHZ)
>>>
>>> -Example:
>>> +Optional properties for compatible string qcom,wcn3990-bt:
>>> +
>>> + - vddio-supply: Bluetooth wcn3990 VDD_IO supply regulator handle.
>>> + - vddxo-supply: Bluetooth wcn3990 VDD_XO supply regulator handle.
>>> + - vddrf-supply: Bluetooth wcn3990 VDD_RF supply regulator handle.
>>> + - vddch0-supply: Bluetooth wcn3990 VDD_CH0 supply regulator handle.
>>
>> Are these really optional? If I understand correctly the driver
>> expects the regulators to be there. Even if it could do with only some
>> regulators specified the devm_regulator_bulk_get() call would fail if
>> not all requested regulators are available.
>
> yes they are required along with compatible string "qcom,wcn3990-bt".
> i have taken reference wrt compatible string "qcom,qca6174-bt".
> In which clocks and enable-gpios are required for driver to work, but
> it was written as optional in doc.
>
> below snippet from hci_qca.c for qcom,qca6174-bt.
>
> if (IS_ERR(qcadev->bt_en)) {
> dev_err(&serdev->dev, "failed to acquire enable gpio\n");
> return PTR_ERR(qcadev->bt_en);
> }
>
> qcadev->susclk = devm_clk_get(&serdev->dev, NULL);
> if (IS_ERR(qcadev->susclk)) {
> dev_err(&serdev->dev, "failed to acquire clk\n");
> return PTR_ERR(qcadev->susclk);
> }
technically it is not correct then i will update as below
Required properties for compatible string qcom,wcn3990-bt:
- vddio-supply: Bluetooth wcn3990 VDD_IO supply regulator handle.
- vddxo-supply: Bluetooth wcn3990 VDD_XO supply regulator handle.
- vddrf-supply: Bluetooth wcn3990 VDD_RF supply regulator handle.
- vddch0-supply: Bluetooth wcn3990 VDD_CH0 supply regulator handle.
Optional properties for compatible string qcom,wcn3990-bt:
- max-speed: see
Documentation/devicetree/bindings/serial/slave-device.txt
are they above ok?
--
Regards
Balakrishna.
next prev parent reply other threads:[~2018-08-02 18:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 13:25 [PATCH v12 0/7] Enable Bluetooth functionality for WCN3990 Balakrishna Godavarthi
2018-08-02 13:25 ` [PATCH v12 1/7] dt-bindings: net: bluetooth: Add device tree bindings for QTI chip wcn3990 Balakrishna Godavarthi
2018-08-02 15:29 ` Stephen Boyd
2018-08-02 17:20 ` Matthias Kaehlcke
2018-08-02 17:54 ` Balakrishna Godavarthi
2018-08-02 18:05 ` Balakrishna Godavarthi [this message]
2018-08-02 18:10 ` Matthias Kaehlcke
2018-08-02 18:12 ` Balakrishna Godavarthi
2018-08-02 13:25 ` [PATCH v12 2/7] Bluetooth: btqca: Rename ROME specific functions to generic functions Balakrishna Godavarthi
2018-08-02 13:25 ` [PATCH v12 3/7] Bluetooth: btqca: Redefine qca_uart_setup() to generic function Balakrishna Godavarthi
2018-08-02 13:25 ` [PATCH v12 4/7] Bluetooth: hci_qca: Add wrapper functions for setting UART speed Balakrishna Godavarthi
2018-08-02 13:25 ` [PATCH v12 5/7] Bluetooth: hci_qca: Enable 3.2 Mbps operating speed Balakrishna Godavarthi
2018-08-02 13:25 ` [PATCH v12 6/7] Bluetooth: btqca: Add wcn3990 firmware download support Balakrishna Godavarthi
2018-08-02 13:25 ` [PATCH v12 7/7] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth chip wcn3990 Balakrishna Godavarthi
2018-08-02 17:15 ` Matthias Kaehlcke
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=58791a55af5532d476febddea6756fdb@codeaurora.org \
--to=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=mka@chromium.org \
--cc=rtatiya@codeaurora.org \
--cc=thierry.escande@linaro.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).