Linux bluetooth development
 help / color / mirror / Atom feed
From: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.dentz@gmail.com, quic_mohamull@quicinc.com,
	quic_hbandi@quicinc.com, quic_anubhavg@quicinc.com,
	Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Subject: [PATCH BlueZ v1 0/6] RAP: Move CS default settings
Date: Tue, 30 Jun 2026 15:41:52 +0530	[thread overview]
Message-ID: <20260630101158.2239682-1-naga.akella@oss.qualcomm.com> (raw)

This series removes CS default settings (role, cs_sync_ant_sel, and
max_tx_power) from RAP initialization and configuration paths where they
do not logically belong.

These parameters are measurement-session specific and are already supplied
through StartMeasurement. Keeping them in main.conf and passing them during
HCI attachment introduces unnecessary duplication and mixes per-session
configuration with device initialization.

The changes in this series:

  1. Remove CS default settings from main.conf parsing and configuration.
  2. Update bt_rap_attach_hci() callers to stop passing these parameters.
  3. Simplify bt_rap_attach_hci() by removing the corresponding arguments.
  4. Remove wrapper API

Naga Bhavani Akella (6):
  shared: remove default settings params from bt_rap_attach_hci
  profiles: update bt_rap_attach_hci call to drop default settings args
  rap: remove CS default settings from main.conf
  shared: replace the wrapper API
  profiles: replace wrapper API
  shared: remove wrapper API

 profiles/ranging/rap.c     |   5 +-
 profiles/ranging/rap_hci.c |  27 +++-----
 src/btd.h                  |   7 --
 src/main.c                 | 127 +------------------------------------
 src/main.conf              |  24 -------
 src/shared/rap.h           |   4 +-
 6 files changed, 13 insertions(+), 181 deletions(-)

-- 


             reply	other threads:[~2026-06-30 10:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 10:11 Naga Bhavani Akella [this message]
2026-06-30 10:11 ` [PATCH BlueZ v1 1/6] shared: remove default settings params from bt_rap_attach_hci Naga Bhavani Akella
2026-06-30 12:20   ` RAP: Move CS default settings bluez.test.bot
2026-06-30 10:11 ` [PATCH BlueZ v1 2/6] profiles: update bt_rap_attach_hci call to drop default settings args Naga Bhavani Akella
2026-06-30 10:11 ` [PATCH BlueZ v1 3/6] rap: remove CS default settings from main.conf Naga Bhavani Akella
2026-06-30 10:11 ` [PATCH BlueZ v1 4/6] shared: replace the wrapper API Naga Bhavani Akella
2026-06-30 10:11 ` [PATCH BlueZ v1 5/6] profiles: replace " Naga Bhavani Akella
2026-06-30 10:11 ` [PATCH BlueZ v1 6/6] shared: remove " Naga Bhavani Akella

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=20260630101158.2239682-1-naga.akella@oss.qualcomm.com \
    --to=naga.akella@oss.qualcomm.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=quic_anubhavg@quicinc.com \
    --cc=quic_hbandi@quicinc.com \
    --cc=quic_mohamull@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox