[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <jztfgic2kbziqradykdmyqv6st3lue23snweawlxtmprqd3ifu@t3gw2o4g5qfx>
Date: Fri, 7 Nov 2025 05:13:53 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Shuai Zhang <quic_shuaz@...cinc.com>
Cc: Marcel Holtmann <marcel@...tmann.org>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>,
linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, linux-arm-msm@...r.kernel.org,
quic_chejiang@...cinc.com, quic_jiaymao@...cinc.com,
quic_chezhou@...cinc.com
Subject: Re: [PATCH v1] Bluetooth: btusb: add new custom firmwares
On Fri, Nov 07, 2025 at 10:13:45AM +0800, Shuai Zhang wrote:
> There are custom-made firmwares based on board ID for a given QCA BT
> chip sometimes, and they are different with existing firmwares and put
> in a separate subdirectory to avoid conflict, for example:
> QCA2066, as a variant of WCN6855, has firmwares under 'qca/QCA2066/'
> of linux-firmware repository.
These are generic phrases regarding QCA2066. Describe why and what is
done in the patch (e.g. why do you add new entry to that table).
>
> Cc: stable@...r.kernel.org
There is little point for CC'ing stable if this is not a fix (and it's
not, it lacks a corresponding tag).
> Signed-off-by: Shuai Zhang <quic_shuaz@...cinc.com>
Please migrate to the @oss.qualcomm.com address.
> ---
> drivers/bluetooth/btusb.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index dcbff7641..7175e9b2d 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -3273,6 +3273,7 @@ static const struct qca_device_info qca_devices_table[] = {
>
> static const struct qca_custom_firmware qca_custom_btfws[] = {
> { 0x00130201, 0x030A, "QCA2066" },
> + { 0x00130201, 0x030B, "QCA2066" },
> { },
> };
>
> --
> 2.34.1
>
--
With best wishes
Dmitry
Powered by blists - more mailing lists