From: Hans de Goede <hdegoede@redhat.com>
To: Ismael Ferreras Morezuelas <swyterzone@gmail.com>, marcel@holtmann.org
Cc: johan.hedberg@gmail.com, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
pmenzel@molgen.mpg.de
Subject: Re: [PATCH v4 1/2] Bluetooth: hci_sync: Add a new quirk to skip HCI_FLT_CLEAR_ALL
Date: Tue, 8 Mar 2022 08:53:04 +0100 [thread overview]
Message-ID: <72d66def-e23e-0029-6d52-3fbf3cf22849@redhat.com> (raw)
In-Reply-To: <20220307200445.5554-1-swyterzone@gmail.com>
Hi,
On 3/7/22 21:04, Ismael Ferreras Morezuelas wrote:
> Some controllers have problems with being sent a command to clear
> all filtering. While the HCI code does not unconditionally
> send a clear-all anymore at BR/EDR setup (after the state machine
> refactor), there might be more ways of hitting these codepaths
> in the future as the kernel develops.
>
> Cc: stable@vger.kernel.org
> Cc: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Ismael Ferreras Morezuelas <swyterzone@gmail.com>
Thanks, the series looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
for both patches.
Regards,
Hans
> ---
> include/net/bluetooth/hci.h | 10 ++++++++++
> net/bluetooth/hci_sync.c | 16 ++++++++++++++++
> 2 files changed, 26 insertions(+)
>
> diff --git a/include/net/bluetooth/hci.h b/include/net/bluetooth/hci.h
> index 35c073d44ec5..5cb095b09a94 100644
> --- a/include/net/bluetooth/hci.h
> +++ b/include/net/bluetooth/hci.h
> @@ -255,6 +255,16 @@ enum {
> * during the hdev->setup vendor callback.
> */
> HCI_QUIRK_BROKEN_READ_TRANSMIT_POWER,
> +
> + /* When this quirk is set, HCI_OP_SET_EVENT_FLT requests with
> + * HCI_FLT_CLEAR_ALL are ignored and event filtering is
> + * completely avoided. A subset of the CSR controller
> + * clones struggle with this and instantly lock up.
> + *
> + * Note that devices using this must (separately) disable
> + * runtime suspend, because event filtering takes place there.
> + */
> + HCI_QUIRK_BROKEN_FILTER_CLEAR_ALL,
> };
>
> /* HCI device flags */
> diff --git a/net/bluetooth/hci_sync.c b/net/bluetooth/hci_sync.c
> index e31d1150dc71..c3bdaf2de511 100644
> --- a/net/bluetooth/hci_sync.c
> +++ b/net/bluetooth/hci_sync.c
> @@ -2812,6 +2812,9 @@ static int hci_set_event_filter_sync(struct hci_dev *hdev, u8 flt_type,
> if (!hci_dev_test_flag(hdev, HCI_BREDR_ENABLED))
> return 0;
>
> + if (test_bit(HCI_QUIRK_BROKEN_FILTER_CLEAR_ALL, &hdev->quirks))
> + return 0;
> +
> memset(&cp, 0, sizeof(cp));
> cp.flt_type = flt_type;
>
> @@ -2832,6 +2835,13 @@ static int hci_clear_event_filter_sync(struct hci_dev *hdev)
> if (!hci_dev_test_flag(hdev, HCI_EVENT_FILTER_CONFIGURED))
> return 0;
>
> + /* In theory the state machine should not reach here unless
> + * a hci_set_event_filter_sync() call succeeds, but we do
> + * the check both for parity and as a future reminder.
> + */
> + if (test_bit(HCI_QUIRK_BROKEN_FILTER_CLEAR_ALL, &hdev->quirks))
> + return 0;
> +
> return hci_set_event_filter_sync(hdev, HCI_FLT_CLEAR_ALL, 0x00,
> BDADDR_ANY, 0x00);
> }
> @@ -4831,6 +4841,12 @@ static int hci_update_event_filter_sync(struct hci_dev *hdev)
> if (!hci_dev_test_flag(hdev, HCI_BREDR_ENABLED))
> return 0;
>
> + /* Some fake CSR controllers lock up after setting this type of
> + * filter, so avoid sending the request altogether.
> + */
> + if (test_bit(HCI_QUIRK_BROKEN_FILTER_CLEAR_ALL, &hdev->quirks))
> + return 0;
> +
> /* Always clear event filter when starting */
> hci_clear_event_filter_sync(hdev);
>
next prev parent reply other threads:[~2022-03-08 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 20:04 [PATCH v4 1/2] Bluetooth: hci_sync: Add a new quirk to skip HCI_FLT_CLEAR_ALL Ismael Ferreras Morezuelas
2022-03-07 20:04 ` [PATCH v4 2/2] Bluetooth: btusb: Use quirk to skip HCI_FLT_CLEAR_ALL on fake CSR controllers Ismael Ferreras Morezuelas
2022-03-08 7:53 ` Hans de Goede [this message]
2022-03-10 9:56 ` [PATCH v4 1/2] Bluetooth: hci_sync: Add a new quirk to skip HCI_FLT_CLEAR_ALL Marcel Holtmann
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=72d66def-e23e-0029-6d52-3fbf3cf22849@redhat.com \
--to=hdegoede@redhat.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=swyterzone@gmail.com \
/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