From: Balakrishna Godavarthi <bgodavar@codeaurora.org>
To: marcel@holtmann.org, johan.hedberg@gmail.com, mka@chromium.org
Cc: 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 v13 0/7] Enable Bluetooth functionality for WCN3990
Date: Fri, 03 Aug 2018 00:39:26 +0530 [thread overview]
Message-ID: <94dbf53da5a77bbc345f3246f06f7e4f@codeaurora.org> (raw)
In-Reply-To: <20180802190732.4811-1-bgodavar@codeaurora.org>
my bad forgot to add subject.
On 2018-08-03 00:37, Balakrishna Godavarthi wrote:
> These patches enables Bluetooth functinalties for new Qualcomm
> Bluetooth chip wnc3990. As this is latest chip with new features,
> along with some common features to old chip "qcom,qca6174-bt".
> we have updated names of functions that are used for both the chips
> to keep this generic and would help in future when we would have new
> BT SoC.
>
> The below are difference between new and old chips.
>
> *Power:
> *New chip: we use voltage regulators to turn on/off the chip and we
> must send a command on Tx line to turn on/off the chip completely.
> *Old chip: We turn on/off by setting a GPIO.
>
> *Note: Turning on sequence differs between two chips.
>
> *Firmware download:
> Only firmware file name differ from New and Old chip.
>
> So we reused some functions/structure/variables which are used for
> old
> chip to New chip by generic naming (may be future chips may use same
> functions).
>
> * As we have multiple changes for functions names,we have tested these
> patches
> on both chips.
>
> v13:
> * Segregated optional and required properties for wcn3990.
>
> v12:
> * removed iteration loop in qca_init_wcn3990
> * updated review comments.
>
> v11:
> * removed regulator current from dtbindings
> * addressed review comments.
>
> v10:
> * update current load with actual values of WCN3990.
> * added support for itterative connect with BT chip if it fails to
> respond to the HOST.
> * Added regulator current dtbindings.
> * addressed review comments.
>
> v9:
> * removed smps regs.
> * hidded flow control in respective functions.
> * moved qca_soc_ver to qca_setup
> * addressed review comments.
>
> v8:
> * Squashed [v7 2/8] and [v7 3/8] to one patch.
> * updated functions to set and get the UART speeds.
> * addressed review comments.
>
> v7:
> * Renamed all the possible function of ROME to generic.
> * updated with review comments for hci_qca and btqca
> * fixed kbuild errors.
> * created wrapper functions for re-usable blocks.
>
> v6:
> * Hooked up qca_power to qca_serdev.
> * renamed all the naming inconsistency functions with qca_*
> * leveraged common code of ROME for wcn3990.
> * created wrapper functions for re-usable blocks.
> * updated function of _*regulator_enable and _*regualtor_disable.
> * removed redundant comments and functions.
> * add code to derive the firmware files based on ROM Version.
> * created new patch for common function of ROME and wcn3990.
> * enables Qualcomm chip to operate at 3.2Mbps.
> * updated names of functions that are used for both the chips to
> keep this generic.
>
> v5:
> * updated with review comments for hci_qca and btqca
>
> v4:
> * rebased all changes on top of bluetooth-next.
> * addressed review comments.
> * New patch created for firmware download.
>
> v3:
> * Rebased all changes on top of bluetooth-next.
> * dt-bindings: net: bluetooth: Add device tree bindings for QTI chip
> wcn3990
> - added dt-binding snippet for bluetooth chip wcn3990.
> * Bluetooth: Add support for wcn3990 soc.
> - updated BT_INFO with bt_dev_info, where ever necessary.
>
> v2:
> * Add support for wcn3990:
> These changes are aligned as per serdev frame work.
> We implemented these changes on top of
> https://patchwork.kernel.org/patch/10316093/
> As this patch enable serdev for one of the Qualcomm BT chip.
>
> The changes in the patch include.
> - Adding support to voting up/down regulators for WCN3990.
> - Bluetooth firmware download for wcn3990.
>
> * Add device tree bindings for Atheros chips:
> These changes are on top of
> https://patchwork.kernel.org/patch/10316097/.
> - Description of device tree bindings.
>
> Balakrishna Godavarthi (7):
> dt-bindings: net: bluetooth: Add device tree bindings for QTI chip
> wcn3990
> Bluetooth: btqca: Rename ROME specific functions to generic functions
> Bluetooth: btqca: Redefine qca_uart_setup() to generic function.
> Bluetooth: hci_qca: Add wrapper functions for setting UART speed
> Bluetooth: hci_qca: Enable 3.2 Mbps operating speed.
> Bluetooth: btqca: Add wcn3990 firmware download support.
> Bluetooth: hci_qca: Add support for Qualcomm Bluetooth chip wcn3990
>
> .../bindings/net/qualcomm-bluetooth.txt | 29 +-
> drivers/bluetooth/btqca.c | 117 +++--
> drivers/bluetooth/btqca.h | 22 +-
> drivers/bluetooth/hci_qca.c | 483 +++++++++++++++---
> 4 files changed, 535 insertions(+), 116 deletions(-)
--
Regards
Balakrishna.
prev parent reply other threads:[~2018-08-02 19:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 19:07 [PATCH v13 0/7] Balakrishna Godavarthi
2018-08-02 19:07 ` [PATCH v13 1/7] dt-bindings: net: bluetooth: Add device tree bindings for QTI chip wcn3990 Balakrishna Godavarthi
2018-08-02 19:39 ` Matthias Kaehlcke
2018-08-02 19:07 ` [PATCH v13 2/7] Bluetooth: btqca: Rename ROME specific functions to generic functions Balakrishna Godavarthi
2018-08-02 19:07 ` [PATCH v13 3/7] Bluetooth: btqca: Redefine qca_uart_setup() to generic function Balakrishna Godavarthi
2018-08-02 19:07 ` [PATCH v13 4/7] Bluetooth: hci_qca: Add wrapper functions for setting UART speed Balakrishna Godavarthi
2018-08-02 19:07 ` [PATCH v13 5/7] Bluetooth: hci_qca: Enable 3.2 Mbps operating speed Balakrishna Godavarthi
2018-08-02 19:07 ` [PATCH v13 6/7] Bluetooth: btqca: Add wcn3990 firmware download support Balakrishna Godavarthi
2018-08-02 19:07 ` [PATCH v13 7/7] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth chip wcn3990 Balakrishna Godavarthi
2018-08-02 19:57 ` Matthias Kaehlcke
2018-08-02 20:10 ` Balakrishna Godavarthi
2018-08-02 20:59 ` Matthias Kaehlcke
2018-08-02 19:09 ` Balakrishna Godavarthi [this message]
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=94dbf53da5a77bbc345f3246f06f7e4f@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).