[bluez/bluez] 26d1de: shared/rap: Add bcs_procedure_data aggregation and...

[bluez/bluez] 26d1de: shared/rap: Add bcs_procedure_data aggregation and...

[Bhavani]

  Branch: refs/heads/1136563
  Home:   https://github.com/bluez/bluez
  Commit: 26d1de5e4c12686df8565bc796df00631bc9076c
      https://github.com/bluez/bluez/commit/26d1de5e4c12686df8565bc796df00631bc9076c
  Author: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
  Date:   2026-07-29 (Wed, 29 Jul 2026)

  Changed paths:
    M src/shared/rap.c
    M src/shared/rap.h

  Log Message:
  -----------
  shared/rap: Add bcs_procedure_data aggregation and procedure data API

Define bcs_procedure_data to hold per-procedure CS results from both
the local initiator and remote reflector, including subevent step data,
selected TX powers, procedure enable config, CS config, sw_time values,
and BLE connection interval.

Add cs_proc_state with a 16-entry ring buffer in cstracker to track
procedures keyed by procedure counter, accumulating results
independently from each side until both report all-results-complete.

Update parse_mode_{0,1,2,3}, parse_step, and parse_subevent_steps with
output pointer parameters to capture remote reflector step data.
Introduce parse_cs_local_initiator_data() to store local HCI subevent
results, handling both initial and continuation events. Update
parse_ras_data_segments() to route decoded RAS subevent data into the
matching cs_proc_state as reflector results.

Add bt_rap_set_procedure_data_cb() to register a callback fired once
both local and remote results are complete for a given procedure.
Add bt_rap_set_local_sw_time(), bt_rap_set_remote_sw_time(), and
bt_rap_set_conn_interval() so callers such as rap_hci.c can supply the
CS capability sw_time and connection interval required by upper-layer
distance calculation algorithms.

Remove unwanted function rap_detached , fix for rap profile level
disconnections


  Commit: f98e4a98e84e347e5795046e06313a1ad63ee55c
      https://github.com/bluez/bluez/commit/f98e4a98e84e347e5795046e06313a1ad63ee55c
  Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
  Date:   2026-07-29 (Wed, 29 Jul 2026)

  Changed paths:
    M profiles/ranging/rap.c
    M profiles/ranging/rap_hci.c

  Log Message:
  -----------
  profiles/ranging: Emit CS ProcedureData signal over D-Bus

Serialize completed BCS procedure data (subevent/step results,
CS config, and procedure-enable parameters) into a byte blob and
emit it via a new ProcedureData D-Bus signal on the CS interface,
so an external ranging estimation daemon can consume raw controller
measurements


  Commit: 417b3d11164f593a3a802c24d950bf9c7b1a7d32
      https://github.com/bluez/bluez/commit/417b3d11164f593a3a802c24d950bf9c7b1a7d32
  Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
  Date:   2026-07-29 (Wed, 29 Jul 2026)

  Changed paths:
    M doc/org.bluez.ChannelSounding1.rst

  Log Message:
  -----------
  doc: Update ProcedureData signal doc for byte-blob format

Document the create_context CS configuration parameter added
alongside the CS Create Config command.

Update the ProcedureData signal signature from dict to array{byte},
matching the byte-blob serialization now used in rap.c, and drop
the per-field dict documentation (procedureCounter, subevent
results, csConfigParam, etc.) that no longer applies since the
signal now carries an opaque binary blob instead of a structured
dict.


Compare: https://github.com/bluez/bluez/compare/26d1de5e4c12%5E...417b3d11164f

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