RE: Bluetooth: hci_qca: Refactor HFP hardware offload capability handling

RE: Bluetooth: hci_qca: Refactor HFP hardware offload capability handling

[bluez.test.bot]

[-- Attachment #1: Type: text/plain, Size: 2861 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1046029

---Test result---

Test Summary:
CheckPatch                    PENDING   0.45 seconds
GitLint                       PENDING   0.39 seconds
SubjectPrefix                 PASS      0.15 seconds
BuildKernel                   PASS      22.62 seconds
CheckAllWarning               PASS      25.33 seconds
CheckSparse                   PASS      27.72 seconds
BuildKernel32                 PASS      22.33 seconds
TestRunnerSetup               PASS      500.06 seconds
TestRunner_l2cap-tester       FAIL      27.84 seconds
TestRunner_iso-tester         PASS      70.76 seconds
TestRunner_bnep-tester        PASS      6.26 seconds
TestRunner_mgmt-tester        FAIL      119.66 seconds
TestRunner_rfcomm-tester      PASS      9.36 seconds
TestRunner_sco-tester         FAIL      14.22 seconds
TestRunner_ioctl-tester       PASS      10.08 seconds
TestRunner_mesh-tester        FAIL      10.42 seconds
TestRunner_smp-tester         PASS      8.44 seconds
TestRunner_userchan-tester    PASS      6.57 seconds
IncrementalBuild              PENDING   0.45 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Total: 96, Passed: 95 (99.0%), Failed: 1, Not Run: 0

Failed Test Cases
L2CAP BR/EDR Client - Set PHY 3M                     Failed       0.110 seconds
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4

Failed Test Cases
Read Exp Feature - Success                           Failed       0.104 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0

Failed Test Cases
Mesh - Send cancel - 1                               Failed       0.129 seconds
Mesh - Send cancel - 2                               Timed out    2.694 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth

[PATCH v2 0/2] Bluetooth: hci_qca: Refactor HFP hardware offload capability handling

[Mengshi Wu]

Changes from v2:
 - Add QCA_CAP_HFP_HW_OFFLOAD capability flag at first commit to avoid
   breaking original logic.

Changes from v1:
 - Refactor HFP hardware offload capability handling.
 - Enable HFP hardware offload for QCA2066 and WCN6855.
 - Link to v1:
   https://lore.kernel.org/all/20260123055243.2634107-1-mengshi.wu@oss.qualcomm.com/

Mengshi Wu (2):
  Bluetooth: hci_qca: Refactor HFP hardware offload capability handling
  Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

 drivers/bluetooth/hci_qca.c | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

-- 
2.34.1

[PATCH v2 1/2] Bluetooth: hci_qca: Refactor HFP hardware offload capability handling

[Mengshi Wu]

Replace SoC-specific check with capability-based approach for HFP
hardware offload configuration. Add QCA_CAP_HFP_HW_OFFLOAD capability
flag and support_hfp_hw_offload field to qca_serdev structure. Add
QCA_CAP_HFP_HW_OFFLOAD capability flag to QCA2066 device data
structures.

Signed-off-by: Mengshi Wu <mengshi.wu@oss.qualcomm.com>
---
 drivers/bluetooth/hci_qca.c | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
index 888176b0f..b99fdda88 100644
--- a/drivers/bluetooth/hci_qca.c
+++ b/drivers/bluetooth/hci_qca.c
@@ -87,6 +87,7 @@ enum qca_flags {
 enum qca_capabilities {
 	QCA_CAP_WIDEBAND_SPEECH = BIT(0),
 	QCA_CAP_VALID_LE_STATES = BIT(1),
+	QCA_CAP_HFP_HW_OFFLOAD  = BIT(2),
 };
 
 /* HCI_IBS transmit side sleep protocol states */
@@ -229,6 +230,7 @@ struct qca_serdev {
 	u32 init_speed;
 	u32 oper_speed;
 	bool bdaddr_property_broken;
+	bool support_hfp_hw_offload;
 	const char *firmware_name[2];
 };
 
@@ -1879,7 +1881,7 @@ static int qca_setup(struct hci_uart *hu)
 	const char *rampatch_name = qca_get_rampatch_name(hu);
 	int ret;
 	struct qca_btsoc_version ver;
-	struct qca_serdev *qcadev;
+	struct qca_serdev *qcadev = serdev_device_get_drvdata(hu->serdev);
 	const char *soc_name;
 
 	ret = qca_check_speeds(hu);
@@ -1943,7 +1945,6 @@ static int qca_setup(struct hci_uart *hu)
 	case QCA_WCN6750:
 	case QCA_WCN6855:
 	case QCA_WCN7850:
-		qcadev = serdev_device_get_drvdata(hu->serdev);
 		if (qcadev->bdaddr_property_broken)
 			hci_set_quirk(hdev, HCI_QUIRK_BDADDR_PROPERTY_BROKEN);
 
@@ -2033,7 +2034,7 @@ static int qca_setup(struct hci_uart *hu)
 	else
 		hu->hdev->set_bdaddr = qca_set_bdaddr;
 
-	if (soc_type == QCA_QCA2066)
+	if (qcadev->support_hfp_hw_offload)
 		qca_configure_hfp_offload(hdev);
 
 	qca->fw_version = le16_to_cpu(ver.patch_ver);
@@ -2117,7 +2118,8 @@ static const struct qca_device_data qca_soc_data_wcn3998 __maybe_unused = {
 static const struct qca_device_data qca_soc_data_qca2066 __maybe_unused = {
 	.soc_type = QCA_QCA2066,
 	.num_vregs = 0,
-	.capabilities = QCA_CAP_WIDEBAND_SPEECH | QCA_CAP_VALID_LE_STATES,
+	.capabilities = QCA_CAP_WIDEBAND_SPEECH | QCA_CAP_VALID_LE_STATES |
+			QCA_CAP_HFP_HW_OFFLOAD,
 };
 
 static const struct qca_device_data qca_soc_data_qca6390 __maybe_unused = {
@@ -2502,6 +2504,9 @@ static int qca_serdev_probe(struct serdev_device *serdev)
 
 		if (!(data->capabilities & QCA_CAP_VALID_LE_STATES))
 			hci_set_quirk(hdev, HCI_QUIRK_BROKEN_LE_STATES);
+
+		if (data->capabilities & QCA_CAP_HFP_HW_OFFLOAD)
+			qcadev->support_hfp_hw_offload = true;
 	}
 
 	return 0;
-- 
2.34.1

[PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Mengshi Wu]

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(-)

diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
index b99fdda88..212a92bbf 100644
--- a/drivers/bluetooth/hci_qca.c
+++ b/drivers/bluetooth/hci_qca.c
@@ -2155,7 +2155,8 @@ static const struct qca_device_data qca_soc_data_wcn6855 __maybe_unused = {
 		{ "vddrfa1p2", 257000 },
 	},
 	.num_vregs = 6,
-	.capabilities = QCA_CAP_WIDEBAND_SPEECH | QCA_CAP_VALID_LE_STATES,
+	.capabilities = QCA_CAP_WIDEBAND_SPEECH | QCA_CAP_VALID_LE_STATES |
+			QCA_CAP_HFP_HW_OFFLOAD,
 };
 
 static const struct qca_device_data qca_soc_data_wcn7850 __maybe_unused = {
-- 
2.34.1

RE: Bluetooth: hci_qca: Refactor HFP hardware offload capability handling

[bluez.test.bot]

[-- Attachment #1: Type: text/plain, Size: 2672 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1047176

---Test result---

Test Summary:
CheckPatch                    PENDING   0.45 seconds
GitLint                       PENDING   0.47 seconds
SubjectPrefix                 PASS      0.12 seconds
BuildKernel                   PASS      25.26 seconds
CheckAllWarning               PASS      27.50 seconds
CheckSparse                   PASS      31.06 seconds
BuildKernel32                 PASS      24.66 seconds
TestRunnerSetup               PASS      550.08 seconds
TestRunner_l2cap-tester       PASS      28.06 seconds
TestRunner_iso-tester         PASS      67.01 seconds
TestRunner_bnep-tester        PASS      6.11 seconds
TestRunner_mgmt-tester        FAIL      117.00 seconds
TestRunner_rfcomm-tester      PASS      9.27 seconds
TestRunner_sco-tester         FAIL      14.41 seconds
TestRunner_ioctl-tester       PASS      9.96 seconds
TestRunner_mesh-tester        FAIL      12.55 seconds
TestRunner_smp-tester         PASS      8.55 seconds
TestRunner_userchan-tester    PASS      6.54 seconds
IncrementalBuild              PENDING   0.95 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 488 (98.8%), Failed: 2, Not Run: 4

Failed Test Cases
Read Exp Feature - Success                           Failed       0.105 seconds
LL Privacy - Start Discovery 2 (Disable RL)          Failed       0.182 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0

Failed Test Cases
Mesh - Send cancel - 1                               Timed out    2.776 seconds
Mesh - Send cancel - 2                               Timed out    1.996 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth

Re: [PATCH v2 1/2] Bluetooth: hci_qca: Refactor HFP hardware offload capability handling

[Dmitry Baryshkov]

On Tue, Jan 27, 2026 at 12:24:43AM +0800, Mengshi Wu wrote:
> Replace SoC-specific check with capability-based approach for HFP
> hardware offload configuration. Add QCA_CAP_HFP_HW_OFFLOAD capability
> flag and support_hfp_hw_offload field to qca_serdev structure. Add
> QCA_CAP_HFP_HW_OFFLOAD capability flag to QCA2066 device data
> structures.
> 
> Signed-off-by: Mengshi Wu <mengshi.wu@oss.qualcomm.com>
> ---
>  drivers/bluetooth/hci_qca.c | 13 +++++++++----
>  1 file changed, 9 insertions(+), 4 deletions(-)
> 

Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>


-- 
With best wishes
Dmitry

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Dmitry Baryshkov]

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?

-- 
With best wishes
Dmitry

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Mengshi Wu]

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.

RE: Bluetooth: hci_qca: Refactor HFP hardware offload capability handling

[bluez.test.bot]

[-- Attachment #1: Type: text/plain, Size: 2593 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1047345

---Test result---

Test Summary:
CheckPatch                    PENDING   0.28 seconds
GitLint                       PENDING   0.22 seconds
SubjectPrefix                 PASS      0.26 seconds
BuildKernel                   PASS      25.18 seconds
CheckAllWarning               PASS      27.98 seconds
CheckSparse                   PASS      31.47 seconds
BuildKernel32                 PASS      25.12 seconds
TestRunnerSetup               PASS      557.27 seconds
TestRunner_l2cap-tester       PASS      28.78 seconds
TestRunner_iso-tester         PASS      55.61 seconds
TestRunner_bnep-tester        PASS      6.30 seconds
TestRunner_mgmt-tester        FAIL      120.79 seconds
TestRunner_rfcomm-tester      PASS      9.50 seconds
TestRunner_sco-tester         FAIL      14.70 seconds
TestRunner_ioctl-tester       PASS      10.14 seconds
TestRunner_mesh-tester        FAIL      12.50 seconds
TestRunner_smp-tester         PASS      8.57 seconds
TestRunner_userchan-tester    PASS      6.68 seconds
IncrementalBuild              PENDING   0.57 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4

Failed Test Cases
Read Exp Feature - Success                           Failed       0.108 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0

Failed Test Cases
Mesh - Send cancel - 1                               Timed out    2.772 seconds
Mesh - Send cancel - 2                               Timed out    1.996 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Dmitry Baryshkov]

On Tue, Jan 27, 2026 at 10:32:58AM +0800, Mengshi Wu wrote:
> 
> 
> 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.

What does it mean? It either supports HFP ofload, or not. Does it?

-- 
With best wishes
Dmitry

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Luiz Augusto von Dentz]

Hi,

On Tue, Jan 27, 2026 at 10:06 AM Dmitry Baryshkov
<dmitry.baryshkov@oss.qualcomm.com> wrote:
>
> On Tue, Jan 27, 2026 at 10:32:58AM +0800, Mengshi Wu wrote:
> >
> >
> > 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.
>
> What does it mean? It either supports HFP ofload, or not. Does it?

Or does that mean offload is considered the default over HCI, and in
that case does it actually work with the likes of Linux
distros/Pipewire or it is Android only? The fact that it is mentioning
HFP rather than SCO is already concerning to me, the kernel driver
shouldn't be involved with profile layers other than core.


>
> --
> With best wishes
> Dmitry



-- 
Luiz Augusto von Dentz

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Mengshi Wu]

Hi, 

On 1/27/2026 11:06 PM, Dmitry Baryshkov wrote:
> On Tue, Jan 27, 2026 at 10:32:58AM +0800, Mengshi Wu wrote:
>>
>>
>> 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.
> 
> What does it mean? It either supports HFP ofload, or not. Does it?
> 

We have not yet enabled the WCN6750 hardware offload feature from the
software side. Other chips will support this feature subsequently. If
I add the flag too early, it may be kind of misleading since the feature
is not really ready yet.

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Mengshi Wu]

Hi,

On 1/27/2026 11:47 PM, Luiz Augusto von Dentz wrote:
> Hi,
> 
> On Tue, Jan 27, 2026 at 10:06 AM Dmitry Baryshkov
> <dmitry.baryshkov@oss.qualcomm.com> wrote:
>>
>> On Tue, Jan 27, 2026 at 10:32:58AM +0800, Mengshi Wu wrote:
>>>
>>>
>>> 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.
>>
>> What does it mean? It either supports HFP ofload, or not. Does it?
> 
> Or does that mean offload is considered the default over HCI, and in
> that case does it actually work with the likes of Linux
> distros/Pipewire or it is Android only? The fact that it is mentioning
> HFP rather than SCO is already concerning to me, the kernel driver
> shouldn't be involved with profile layers other than core.
> 

Offloading over HCI is the default way for most use cases, but I don't mean
it. Offloading over non-HCI ways (such as I2S, slimbus) need some other
supports from software aspect, these supports for other chips are not ready
yet.

I use HFP because I notice it was used before, like qca_configure_hfp_offload().
Should I correct it if it is not proper here?

> 
>>
>> --
>> With best wishes
>> Dmitry
> 
> 
> 

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Mengshi Wu]

Hi,

On 1/27/2026 11:47 PM, Luiz Augusto von Dentz wrote:
> Hi,
> 
> On Tue, Jan 27, 2026 at 10:06 AM Dmitry Baryshkov
> <dmitry.baryshkov@oss.qualcomm.com> wrote:
>>
>> On Tue, Jan 27, 2026 at 10:32:58AM +0800, Mengshi Wu wrote:
>>>
>>>
>>> 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.
>>
>> What does it mean? It either supports HFP ofload, or not. Does it?
> 
> Or does that mean offload is considered the default over HCI, and in
> that case does it actually work with the likes of Linux
> distros/Pipewire or it is Android only? The fact that it is mentioning
> HFP rather than SCO is already concerning to me, the kernel driver
> shouldn't be involved with profile layers other than core.
> 
> 

Offload over HCI is the default way in most cases, but I don't mean it
here. Offload over non-HCI ways (such as I2S, Slimbus) need other supports
from software aspect, but these supports are not ready for other chips yet.

I use HFP because I noticed that it was used before, like qca_configure_hfp_offload().
Should I change to use SCO if HFP is not proper here?

>>
>> --
>> With best wishes
>> Dmitry
> 
> 
> 

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Dmitry Baryshkov]

On Wed, Jan 28, 2026 at 11:17:49AM +0800, Mengshi Wu wrote:
> Hi, 
> 
> On 1/27/2026 11:06 PM, Dmitry Baryshkov wrote:
> > On Tue, Jan 27, 2026 at 10:32:58AM +0800, Mengshi Wu wrote:
> >>
> >>
> >> 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.
> > 
> > What does it mean? It either supports HFP ofload, or not. Does it?
> > 
> 
> We have not yet enabled the WCN6750 hardware offload feature from the
> software side. Other chips will support this feature subsequently. If
> I add the flag too early, it may be kind of misleading since the feature
> is not really ready yet.

By the software side do you mean BT firmware or something else?

-- 
With best wishes
Dmitry

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Mengshi Wu]

Hi,

On 1/30/2026 10:31 AM, Dmitry Baryshkov wrote:
> On Wed, Jan 28, 2026 at 11:17:49AM +0800, Mengshi Wu wrote:
>> Hi, 
>>
>> On 1/27/2026 11:06 PM, Dmitry Baryshkov wrote:
>>> On Tue, Jan 27, 2026 at 10:32:58AM +0800, Mengshi Wu wrote:
>>>>
>>>>
>>>> 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.
>>>
>>> What does it mean? It either supports HFP ofload, or not. Does it?
>>>
>>
>> We have not yet enabled the WCN6750 hardware offload feature from the
>> software side. Other chips will support this feature subsequently. If
>> I add the flag too early, it may be kind of misleading since the feature
>> is not really ready yet.
> 
> By the software side do you mean BT firmware or something else?
> 
Yes, firmware. And we will update firmware later to support this feature.

Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload for WCN6855

[Dmitry Baryshkov]

On Mon, Feb 02, 2026 at 10:33:53AM +0800, Mengshi Wu wrote:
> Hi,
> 
> On 1/30/2026 10:31 AM, Dmitry Baryshkov wrote:
> > On Wed, Jan 28, 2026 at 11:17:49AM +0800, Mengshi Wu wrote:
> >> Hi, 
> >>
> >> On 1/27/2026 11:06 PM, Dmitry Baryshkov wrote:
> >>> On Tue, Jan 27, 2026 at 10:32:58AM +0800, Mengshi Wu wrote:
> >>>>
> >>>>
> >>>> 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.
> >>>
> >>> What does it mean? It either supports HFP ofload, or not. Does it?
> >>>
> >>
> >> We have not yet enabled the WCN6750 hardware offload feature from the
> >> software side. Other chips will support this feature subsequently. If
> >> I add the flag too early, it may be kind of misleading since the feature
> >> is not really ready yet.
> > 
> > By the software side do you mean BT firmware or something else?
> > 
> Yes, firmware. And we will update firmware later to support this feature.

Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>


-- 
With best wishes
Dmitry