From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 05f685: rap: Add RAS attribute access notification API
Date: Fri, 17 Jul 2026 05:47:02 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1129585/000000-b519f6@github.com> (raw)
Branch: refs/heads/1129585
Home: https://github.com/bluez/bluez
Commit: 05f6854f1088379cad49e051c9f085dbec18d0a4
https://github.com/bluez/bluez/commit/05f6854f1088379cad49e051c9f085dbec18d0a4
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-17 (Fri, 17 Jul 2026)
Changed paths:
M src/shared/rap.c
M src/shared/rap.h
Log Message:
-----------
rap: Add RAS attribute access notification API
Add a callback registration mechanism to notify bt_rap consumers
when a remote peer accesses or discovers a RAS GATT attribute.
Introduce register/unregister APIs and invoke callbacks asynchronously
from all relevant RAS characteristic read/write handlers,
following the existing bt_rap_register() pattern to avoid
reentrancy into device/profile/D-Bus logic.
Commit: b519f6ee42bb1bea70662d091c20c44c186318aa
https://github.com/bluez/bluez/commit/b519f6ee42bb1bea70662d091c20c44c186318aa
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-17 (Fri, 17 Jul 2026)
Changed paths:
M profiles/ranging/rap.c
Log Message:
-----------
profiles: Register RAS UUID reactively instead of probing
Replace the unconditional reflector-role GATT_UUID probe in
gatt_client_init() with a reactive registration driven by actual
remote RAS access, using the notification API added in shared/rap.
Compare: https://github.com/bluez/bluez/compare/05f6854f1088%5E...b519f6ee42bb
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-17 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1129585/000000-b519f6@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/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