[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <35ab1910-76b8-4923-b4ec-f8c104de31c7@oss.qualcomm.com>
Date: Wed, 28 Jan 2026 11:55:16 +0800
From: Mengshi Wu <mengshi.wu@....qualcomm.com>
To: Luiz Augusto von Dentz <luiz.dentz@...il.com>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Bartosz Golaszewski <brgl@...nel.org>,
Marcel Holtmann <marcel@...tmann.org>, linux-arm-msm@...r.kernel.org,
linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
shuai.zhang@....qualcomm.com, cheng.jiang@....qualcomm.com,
chezhou@....qualcomm.com, wei.deng@....qualcomm.com,
yiboz@....qualcomm.com
Subject: Re: [PATCH v2 2/2] Bluetooth: hci_qca: Enable HFP hardware offload
for WCN6855
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@....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@....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
>
>
>
Powered by blists - more mailing lists