From: Marcel Holtmann <marcel@holtmann.org>
To: Balakrishna Godavarthi <bgodavar@codeaurora.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
mka@chromium.org, linux-kernel@vger.kernel.org,
linux-bluetooth@vger.kernel.org, hemantg@codeaurora.org,
linux-arm-msm@vger.kernel.org, tientzu@chromium.org,
seanpaul@chromium.org, bjorn.andersson@linaro.org
Subject: Re: [PATCH v2 0/2] Enable Bluetooth functionality for WCN3991
Date: Sat, 9 Nov 2019 03:28:40 +0100 [thread overview]
Message-ID: <0E5C9575-6D1E-4446-ACEA-B5826A7A6EEC@holtmann.org> (raw)
In-Reply-To: <20191106094832.482-1-bgodavar@codeaurora.org>
Hi Balakrishna,
> These patches enables Bluetooth functinalties for new Qualcomm
> Bluetooth chip wnc3991. As this is latest chip with new features,
> along with some common features to old chip "qcom,qcawcn3991-bt".
> Major difference between old BT SoC's with WCN3991 is WCN3991
> will not send any VSE for the VSC instead is sends the data on CC
> packet.
>
> v2:
> * updated review comments
>
> Balakrishna Godavarthi (2):
> Bluetooth: btqca: Rename ROME specific variables to generic variables
> Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC WCN3991
>
> drivers/bluetooth/btqca.c | 92 ++++++++++++++++++++++++++-----------
> drivers/bluetooth/btqca.h | 32 +++++++------
> drivers/bluetooth/hci_qca.c | 16 ++++++-
> 3 files changed, 97 insertions(+), 43 deletions(-)
both patches have been applied to bluetooth-next tree.
Regards
Marcel
prev parent reply other threads:[~2019-11-09 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:48 [PATCH v2 0/2] Enable Bluetooth functionality for WCN3991 Balakrishna Godavarthi
2019-11-06 9:48 ` [PATCH v2 1/2] Bluetooth: btqca: Rename ROME specific variables to generic variables Balakrishna Godavarthi
2019-11-06 9:48 ` [PATCH v2 2/2] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC WCN3991 Balakrishna Godavarthi
2019-11-09 2:28 ` Marcel Holtmann [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=0E5C9575-6D1E-4446-ACEA-B5826A7A6EEC@holtmann.org \
--to=marcel@holtmann.org \
--cc=bgodavar@codeaurora.org \
--cc=bjorn.andersson@linaro.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=mka@chromium.org \
--cc=seanpaul@chromium.org \
--cc=tientzu@chromium.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).