[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <mt4j2cxliqkwbeprt7ye2kt2cgi2bjfnz2knfgxvy7fy6wda3p@jadb7x7ocagi>
Date: Fri, 23 Jan 2026 21:26:27 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Mengshi Wu <mengshi.wu@....qualcomm.com>
Cc: Bartosz Golaszewski <brgl@...nel.org>,
Marcel Holtmann <marcel@...tmann.org>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>,
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 v1 1/2] Bluetooth: hci_qca: Refactor HFP hardware offload
capability handling
On Fri, Jan 23, 2026 at 01:52:42PM +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.
>
> Signed-off-by: Mengshi Wu <mengshi.wu@....qualcomm.com>
> ---
> drivers/bluetooth/hci_qca.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> @@ -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)
At this point QCA2066 becomes broken until the next commit. This is not
a proper way to do things. At the very least, squash the first chunk of
your next commit into this patch.
> qca_configure_hfp_offload(hdev);
>
> qca->fw_version = le16_to_cpu(ver.patch_ver);
> @@ -2502,6 +2503,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
>
--
With best wishes
Dmitry
Powered by blists - more mailing lists