From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Hilda Wu <hildawu@realtek.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
alex_lu@realsil.com.cn, max.chou@realtek.com, kidman@realtek.com
Subject: Re: [PATCH v3] Bluetooth: btrtl: Set msft ext address filter quirk
Date: Thu, 29 Aug 2024 08:13:53 +0200 [thread overview]
Message-ID: <83b72389-e12b-4224-aed7-736880e2877f@molgen.mpg.de> (raw)
In-Reply-To: <20240829034627.676529-1-hildawu@realtek.com>
Dear Hilda,
Thank you for your patch.
Am 29.08.24 um 05:46 schrieb Hilda Wu:
> For tracking multiple devices concurrently with a condition.
> The patch enables the HCI_QUIRK_USE_MSFT_EXT_ADDRESS_FILTER quirk
> on RTL8852B controller.
Please add the controller name also to the commit message summary.
> The quirk setting is based on this commit.
> Commit 9e14606d8f38 ("Bluetooth: msft: Extended monitor tracking by
> address filter")
… is based on commit 9e14606d8f38 ("Bluetooth: msft: Extended monitor
tracking by address filter").
> With this setting, when a pattern monitor detects a device, this
> feature issues an address monitor for tracking that device. Let the
> original pattern monitor can keep monitor new devices.
Remove *can*?
Please paste possible Linux message before/after the commit into the
commit message.
> Signed-off-by: Hilda Wu <hildawu@realtek.com>
> ---
> Change:
> v3: edit commit log and title
> v2: Add reference commit, update commit description
> ---
> ---
> drivers/bluetooth/btrtl.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/bluetooth/btrtl.c b/drivers/bluetooth/btrtl.c
> index 4c0f551a9975..2d95b3ea046d 100644
> --- a/drivers/bluetooth/btrtl.c
> +++ b/drivers/bluetooth/btrtl.c
> @@ -1308,6 +1308,7 @@ void btrtl_set_quirks(struct hci_dev *hdev, struct btrtl_device_info *btrtl_dev)
> btrealtek_set_flag(hdev, REALTEK_ALT6_CONTINUOUS_TX_CHIP);
>
> if (btrtl_dev->project_id == CHIP_ID_8852A ||
> + btrtl_dev->project_id == CHIP_ID_8852B ||
> btrtl_dev->project_id == CHIP_ID_8852C)
> set_bit(HCI_QUIRK_USE_MSFT_EXT_ADDRESS_FILTER, &hdev->quirks);
Kind regards,
Paul
next prev parent reply other threads:[~2024-08-29 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 3:46 Hilda Wu
2024-08-29 6:13 ` Paul Menzel [this message]
2024-08-29 8:39 ` Hilda Wu
2024-08-30 16:30 ` 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=83b72389-e12b-4224-aed7-736880e2877f@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=alex_lu@realsil.com.cn \
--cc=hildawu@realtek.com \
--cc=kidman@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.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
all inboxes | Powered by JetHome®