Linux bluetooth development
 help / color / mirror / Atom feed
From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 7efd93: shared: rap: Defer CS Event registration until con...
Date: Wed, 24 Jun 2026 10:44:32 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/912f5e-eb9b35@github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: 7efd9383f0a1ea20226c63494bc0bcb9a3e2a8fa
      https://github.com/bluez/bluez/commit/7efd9383f0a1ea20226c63494bc0bcb9a3e2a8fa
  Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
  Date:   2026-06-24 (Wed, 24 Jun 2026)

  Changed paths:
    M profiles/ranging/rap.c

  Log Message:
  -----------
  shared: rap: Defer CS Event registration until connection setup

Move LE CS event registration from rap_probe()
to rap_accept(). rap_probe() runs during service discovery
while no ACL connection or connection handle exists,
so connection-scoped CS events cannot be delivered or
associated with a device. rap_accept() is called
after the ACL link is established, when a valid
connection handle is available and the HCI layer
can route events correctly.
Registering events at this point ensures
proper handling of CS events.


  Commit: 40a58272a58fdfb00081289ab41fa6d4cebfb935
      https://github.com/bluez/bluez/commit/40a58272a58fdfb00081289ab41fa6d4cebfb935
  Author: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
  Date:   2026-06-24 (Wed, 24 Jun 2026)

  Changed paths:
    M src/shared/rap.c

  Log Message:
  -----------
  shared/rap: Fix step payload pointer in parse_step

util_iov_pull advances iov_base before returning the new pointer, so
mode_iov.iov_base was set to the start of the *next* step's data.
Every step was therefore parsed using its successor's bytes.

Switch to util_iov_pull_mem which saves the original base, advances
iov, and returns the pre-advance pointer — correctly pointing to the
current step's payload.


  Commit: eb9b35c8d13dffcaf4f6f4b5bee29a18c860ba04
      https://github.com/bluez/bluez/commit/eb9b35c8d13dffcaf4f6f4b5bee29a18c860ba04
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2026-06-24 (Wed, 24 Jun 2026)

  Changed paths:
    M unit/test-bap.c

  Log Message:
  -----------
  unit: test-bap: disable optimization to speed up compilation

Compilation of this file with optimization takes 12 min with ASAN, 1 min
without.  This is too long, and the -O2 doesn't serve purpose for unit
tests.

Disable optimization to reduce to 30 sec with ASAN (5 sec without).

autoconf puts global -O2 in CFLAGS that cannot be overridden eg. with
unit_test_bap_CFLAGS. Use pragma instead.


Compare: https://github.com/bluez/bluez/compare/912f5efb0dd9...eb9b35c8d13d

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-06-24 17:44 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/master/912f5e-eb9b35@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