All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Xiuzhuo Shang <xiuzhuo.shang@oss.qualcomm.com>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
	cheng.jiang@oss.qualcomm.com, quic_chezhou@quicinc.com,
	wei.deng@oss.qualcomm.com, shuai.zhang@oss.qualcomm.com,
	mengshi.wu@oss.qualcomm.com, jinwang.li@oss.qualcomm.com
Subject: Re: [PATCH] adapter: restrict delta=0 RSSI to proximity filters
Date: Mon, 20 Jul 2026 19:40:08 +0000	[thread overview]
Message-ID: <178457640838.4136385.15524893559590491183.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260715091936.4137598-1-xiuzhuo.shang@oss.qualcomm.com>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed, 15 Jul 2026 17:19:36 +0800 you wrote:
> When a discovery filter is active (filtered_discovery=true), BlueZ
> unconditionally calls device_set_rssi_with_delta(..., delta=0),
> causing every BLE advertisement to emit a PropertiesChanged(RSSI)
> signal regardless of whether the RSSI value changed.
> 
> delta=0 is only needed when a client has expressed explicit proximity
> interest by setting an RSSI or pathloss threshold in its discovery
> filter. Filters that specify only transport type or UUIDs do not
> require per-packet RSSI precision; for those, the standard
> RSSI_THRESHOLD=8 rate-limiting is both correct and desirable.
> 
> [...]

Here is the summary with links:
  - adapter: restrict delta=0 RSSI to proximity filters
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e004414a1751

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-20 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15  9:19 [PATCH] adapter: restrict delta=0 RSSI to proximity filters Xiuzhuo Shang
2026-07-15 10:13 ` bluez.test.bot
2026-07-20 19:40 ` patchwork-bot+bluetooth [this message]

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=178457640838.4136385.15524893559590491183.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=cheng.jiang@oss.qualcomm.com \
    --cc=jinwang.li@oss.qualcomm.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=mengshi.wu@oss.qualcomm.com \
    --cc=quic_chezhou@quicinc.com \
    --cc=shuai.zhang@oss.qualcomm.com \
    --cc=wei.deng@oss.qualcomm.com \
    --cc=xiuzhuo.shang@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.