From: Balakrishna Godavarthi <bgodavar@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,
tientzu@chromium.org, seanpaul@chromium.org,
bjorn.andersson@linaro.org
Subject: [PATCH v2 0/2] Enable Bluetooth functionality for WCN3991
Date: Wed, 6 Nov 2019 15:18:30 +0530 [thread overview]
Message-ID: <20191106094832.482-1-bgodavar@codeaurora.org> (raw)
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(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2019-11-06 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:48 Balakrishna Godavarthi [this message]
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 ` [PATCH v2 0/2] Enable Bluetooth functionality for WCN3991 Marcel Holtmann
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=20191106094832.482-1-bgodavar@codeaurora.org \
--to=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=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.