From: Mengshi Wu <mengshi.wu@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-arm-msm@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, shuai.zhang@oss.qualcomm.com,
cheng.jiang@oss.qualcomm.com, chezhou@qti.qualcomm.com,
wei.deng@oss.qualcomm.com, yiboz@qti.qualcomm.com
Subject: Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855
Date: Tue, 27 Jan 2026 10:32:58 +0800 [thread overview]
Message-ID: <7b9fec28-2272-4ff7-9575-76e72cecada5@oss.qualcomm.com> (raw)
In-Reply-To: <kej5u2hjxjtfdzmgtebns3amz7gmb5d2nciy45jsyglkprgh6s@kt6fodrc3oll>
On 1/27/2026 1:51 AM, Dmitry Baryshkov wrote:
> On Tue, Jan 27, 2026 at 12:24:44AM +0800, Mengshi Wu wrote:
>> Add QCA_CAP_HFP_HW_OFFLOAD capability flag to WCN6855 device
>> data structures to enable Hands-Free Profile (HFP) hardware
>> offload support on these Qualcomm Bluetooth chipsets.
>>
>> Signed-off-by: Mengshi Wu <mengshi.wu@oss.qualcomm.com>
>> ---
>> drivers/bluetooth/hci_qca.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>
> Any other chips which would benefit from this flag? If you are setting
> it for WCN6855, I'd assume that it also applies to WCN7850. Should it be
> set for WCN6750?
>
Thanks for the reminder. This should also apply to WCN7850. WCN6750 is not
considered at this time.
next prev parent reply other threads:[~2026-01-27 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 16:24 [PATCH v2 0/2] Bluetooth: hci_qca: Refactor HFP hardware offload capability handling Mengshi Wu
2026-01-26 16:24 ` [PATCH v2 1/2] " Mengshi Wu
2026-01-26 17:49 ` Dmitry Baryshkov
2026-01-26 16:24 ` [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855 Mengshi Wu
2026-01-26 17:51 ` Dmitry Baryshkov
2026-01-27 2:32 ` Mengshi Wu [this message]
2026-01-27 15:06 ` Dmitry Baryshkov
2026-01-27 15:47 ` Luiz Augusto von Dentz
2026-01-28 3:55 ` Mengshi Wu
2026-01-28 4:03 ` Mengshi Wu
2026-01-28 3:17 ` Mengshi Wu
2026-01-30 2:31 ` Dmitry Baryshkov
2026-02-02 2:33 ` Mengshi Wu
2026-02-04 2:44 ` Dmitry Baryshkov
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=7b9fec28-2272-4ff7-9575-76e72cecada5@oss.qualcomm.com \
--to=mengshi.wu@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=chezhou@qti.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=shuai.zhang@oss.qualcomm.com \
--cc=wei.deng@oss.qualcomm.com \
--cc=yiboz@qti.qualcomm.com \
/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