add new custom firmwares
Please refer to the link for information about the qcs2066 folder.
a3f9f6dd047a ("Bluetooth: btusb: QCA: Support downloading custom-made firmwares")
Changes for v2 - Add a more detailed description of the patch. - remove CC stable - V1 link https://lore.kernel.org/all/20251107021345.2759890-1-quic_shuaz@quicinc.com/
Shuai Zhang (1): Bluetooth: btusb: add new custom firmwares
drivers/bluetooth/btusb.c | 1 + 1 file changed, 1 insertion(+)
The new platform uses the QCA2066 chip along with a new board ID, which requires a dedicated firmware file to ensure proper initialization. Without this entry, the driver cannot locate and load the correct firmware, resulting in Bluetooth bring-up failure.
This patch adds a new entry to the firmware table for QCA2066 so that the driver can correctly identify the board ID and load the appropriate firmware from 'qca/QCA2066/' in the linux-firmware repository.
Signed-off-by: Shuai Zhang quic_shuaz@quicinc.com --- 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" }, { }, };
Hi,
Thanks for your patch.
FYI: kernel test robot notices the stable kernel rule is not satisfied.
The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#opti...
Rule: add the tag "Cc: stable@vger.kernel.org" in the sign-off area to have the patch automatically included in the stable tree. Subject: [PATCH v2 1/1] Bluetooth: btusb: add new custom firmwares Link: https://lore.kernel.org/stable/20251107125405.1632663-2-quic_shuaz%40quicinc...
On Fri, Nov 07, 2025 at 08:56:12PM +0800, kernel test robot wrote:
Hi,
Thanks for your patch.
FYI: kernel test robot notices the stable kernel rule is not satisfied.
The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#opti...
Rule: add the tag "Cc: stable@vger.kernel.org" in the sign-off area to have the patch automatically included in the stable tree. Subject: [PATCH v2 1/1] Bluetooth: btusb: add new custom firmwares Link: https://lore.kernel.org/stable/20251107125405.1632663-2-quic_shuaz%40quicinc...
Shuai, why are you sending a patch which is not a fix for inclusion into the stable tree? Why do you cc:stable in your headers? Do you understand what stable kernels are for?
Hi Dmitry
On 11/7/2025 10:14 PM, Dmitry Baryshkov wrote:
On Fri, Nov 07, 2025 at 08:56:12PM +0800, kernel test robot wrote:
Hi,
Thanks for your patch.
FYI: kernel test robot notices the stable kernel rule is not satisfied.
The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#opti...
Rule: add the tag "Cc: stable@vger.kernel.org" in the sign-off area to have the patch automatically included in the stable tree. Subject: [PATCH v2 1/1] Bluetooth: btusb: add new custom firmwares Link: https://lore.kernel.org/stable/20251107125405.1632663-2-quic_shuaz%40quicinc...
Shuai, why are you sending a patch which is not a fix for inclusion into the stable tree? Why do you cc:stable in your headers? Do you understand what stable kernels are for?
Sorry for the oversight — I forgot to remove the Cc: stable@vger.kernel.org. I will correct this in the next revision. Thank you for pointing it out.
Best regards, Shuai Zhang
linux-stable-mirror@lists.linaro.org
-
Dmitry Baryshkov -
kernel test robot -
Shuai Zhang