The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Pascal Giard <evilynux@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	Pascal Giard <pascal.giard@etsmtl.ca>
Subject: Re: [PATCH v2 1/1] Bluetooth: btusb: Reclassify Qualcomm WCN6855 debug packets
Date: Tue, 7 Oct 2025 18:16:19 +0200	[thread overview]
Message-ID: <a91cf69c-e9d9-40b6-9bba-0308855c3014@molgen.mpg.de> (raw)
In-Reply-To: <20251007153315.72565-1-pascal.giard@etsmtl.ca>

Dear Pascal,


Thank you for your patch.

Am 07.10.25 um 17:33 schrieb Pascal Giard:
> Some Qualcomm Bluetooth controllers, e.g., QCNFA765 with WCN6855
> chip, send debug packets as ACL frames with header 0x2EDC.
> The kernel misinterprets these as malformed ACL packets, causing
> repeated errors:
> 
>    Bluetooth: hci0: ACL packet for unknown connection handle 3804
> 
> This can occur hundreds of times per minute, greatly cluttering logs.
> On my computer, I am observing approximately 7 messages per second
> when streaming audio to a speaker.
> 
> For Qualcomm controllers exchanging over UART, hci_qca.c already
> filters out these debug packets. This patch is for controllers
> not going through UART, but USB.
> 
> This patch uses the classify_pkt_type callback to reclassify the
> packets with handle 0x2EDC as HCI_DIAG_PKT before they reach the
> HCI layer. This change is only applied to Qualcomm devices marked
> as BTUSB_QCA_WCN6855.
> 
> Tested on: Thinkpad T14 gen2 (AMD) with QCNFA765 (0489:E0D0)
> Signed-off-by: Pascal Giard <pascal.giard@etsmtl.ca>
> ---
> Changes in v2:
> - Address reviewer feedback about 0x2EDC being a valid HCI handle
> - Use classify_pkt_type callback instead of filtering in recv_acl
> - Only apply to devices with BTUSB_QCA_WCN6855 quirk

Outstanding commit message!

> ---
>   drivers/bluetooth/btusb.c | 19 +++++++++++++++++++
>   1 file changed, 19 insertions(+)
> 
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 5e9ebf0c5312..256179ace853 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -1131,6 +1131,24 @@ static void btusb_qca_reset(struct hci_dev *hdev)
>   	btusb_reset(hdev);
>   }
>   
> +static u8 btusb_classify_qca_pkt_type(struct hci_dev *hdev, struct sk_buff *skb)
> +{
> +	/* Some Qualcomm controllers, e.g., QCNFA765 with WCN6855 chip, send debug
> +	 * packets as ACL frames with connection handle 0x2EDC. These are not real
> +	 * ACL packets and should be reclassified as HCI_DIAG_PKT to prevent
> +	 * "ACL packet for unknown connection handle 3804" errors.
> +	 */
> +	if (skb->len >= 2) {
> +		u16 handle = get_unaligned_le16(skb->data);
> +
> +		if (handle == 0x2EDC)
> +			return HCI_DIAG_PKT;
> +	}
> +
> +	/* Use default packet type for other packets */
> +	return hci_skb_pkt_type(skb);
> +}
> +
>   static inline void btusb_free_frags(struct btusb_data *data)
>   {
>   	unsigned long flags;
> @@ -4201,6 +4219,7 @@ static int btusb_probe(struct usb_interface *intf,
>   		data->recv_acl = btusb_recv_acl_qca;
>   		hci_devcd_register(hdev, btusb_coredump_qca, btusb_dump_hdr_qca, NULL);
>   		data->setup_on_usb = btusb_setup_qca;
> +		hdev->classify_pkt_type = btusb_classify_qca_pkt_type;
>   		hdev->shutdown = btusb_shutdown_qca;
>   		hdev->set_bdaddr = btusb_set_bdaddr_wcn6855;
>   		hdev->reset = btusb_qca_reset;

Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>


Kind regards,

Paul

  reply	other threads:[~2025-10-07 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 15:33 [PATCH v2 1/1] Bluetooth: btusb: Reclassify Qualcomm WCN6855 debug packets Pascal Giard
2025-10-07 16:16 ` Paul Menzel [this message]
2025-10-22 13:50 ` patchwork-bot+bluetooth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a91cf69c-e9d9-40b6-9bba-0308855c3014@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=evilynux@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pascal.giard@etsmtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox