* [bluez/bluez] bd47bb: shared/rap: Track RAS CCC state per connection
@ 2026-10-09 23:39 Luiz Augusto von Dentz
0 siblings, 0 replies; only message in thread
From: Luiz Augusto von Dentz @ 2026-10-09 23:39 UTC (permalink / raw)
To: linux-bluetooth
Branch: refs/heads/1182593
Home: https://github.com/bluez/bluez
Commit: bd47bb95c5deaa85b2a7ab6a33bb867b5666eed8
https://github.com/bluez/bluez/commit/bd47bb95c5deaa85b2a7ab6a33bb867b5666eed8
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-10-09 (Fri, 09 Oct 2026)
Changed paths:
M src/shared/rap.c
Log Message:
-----------
shared/rap: Track RAS CCC state per connection
The Real-time, On-demand, Ranging Data Ready and Ranging Data Overwritten
CCC values were stored on the RAS service shared by all connections, while
ranging data is sent on the ATT channel of the connection that produced
it. One central's subscription could therefore decide whether, and with
which transport, another central was sent ranging data, and the Real-time
vs On-demand exclusivity check rejected a central because of another
central's configuration.
Store the values on the bt_rap session of the writing connection instead
and use them for the mode, transport and subscription checks.
Fixes: a9b39d71597d ("src/shared: Add RAS packet format and notification support")
Fixes: 2ac9fc0901c4 ("shared/rap: Honor CCCD transport for RAS on-demand ranging data")
Assisted-by: OpenCode:claude-opus-5.5
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-10-09 23:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-09 23:39 [bluez/bluez] bd47bb: shared/rap: Track RAS CCC state per connection Luiz Augusto von Dentz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox