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/2] ranging: mode validation and
Date: Thu, 20 Aug 2026 23:19:08 +0530 [thread overview]
Message-ID: <20260820174910.559116-1-naga.akella@oss.qualcomm.com> (raw)
This patch series introduces validation for Main Mode and Sub Mode
combinations in Channel Sounding configuration and updates the
MaxTxPower option documentation to reflect the supported value range.
Patch 1 adds validation to ensure that only specification compliant
main_mode_type and sub_mode_type combinations are accepted. Invalid
combinations are rejected, and the user is informed of the supported
mode pairings.
Patch 2 updates the MaxTxPower configuration option documentation to
clarify that decimal values are supported within the range of
-127 dBm to 20 dBm. The documentation also notes that the default
value is 20 dBm, corresponding to the maximum transmit power.
Naga Bhavani Akella (2):
src: Modify MaxTxPower option documentation for ChannelSounding
client: Enforce Valid Main Mode and Sub Mode Combinations
client/cs.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++-
src/main.conf | 6 ++--
2 files changed, 78 insertions(+), 4 deletions(-)
--
next reply other threads:[~2026-08-20 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 17:49 Naga Bhavani Akella [this message]
2026-08-20 17:49 ` [PATCH BlueZ v1 1/2] src: Modify MaxTxPower option documentation for ChannelSounding Naga Bhavani Akella
2026-08-20 18:57 ` ranging: mode validation and bluez.test.bot
2026-08-20 17:49 ` [PATCH BlueZ v1 2/2] client: Enforce Valid Main Mode and Sub Mode Combinations 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=20260820174910.559116-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