From: "Frédéric Danis" <frederic.danis@collabora.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ 0/3] client/btpclient: Add GAP extended advertising support
Date: Tue, 19 May 2026 12:55:16 +0200 [thread overview]
Message-ID: <20260519105519.226648-1-frederic.danis@collabora.com> (raw)
The BTP_OP_GAP_SET_EXTENDED_ADVERTISING command is used by at least the
BAP/USR/DISC/BV-01-C test.
Since this opcode is defined as 0x21 (33), it does not fit into the
current fixed-size command bitmap. This series refactors the way
btpclient reports supported auto-PTS commands so it can grow the bitmap
dynamically as needed.
The series also switches GAP advertising data handling to the
advertising type definitions already provided by src/shared/ad.h.
Frédéric Danis (3):
client/btpclient: refactor read-commands bitmap building
client/btpclient: Replace advertising defines by shared ones
client/btpclient: Add BTP_OP_GAP_SET_EXTENDED_ADVERTISING support
client/btpclient/bap.c | 27 ++++--
client/btpclient/btpclient.c | 25 +++++
client/btpclient/btpclient.h | 5 +
client/btpclient/core.c | 29 ++++--
client/btpclient/gap.c | 171 +++++++++++++++++++++++++----------
client/btpclient/gatt.c | 39 +++++---
src/shared/btp.h | 7 ++
7 files changed, 229 insertions(+), 74 deletions(-)
--
2.43.0
next reply other threads:[~2026-05-19 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 10:55 Frédéric Danis [this message]
2026-05-19 10:55 ` [PATCH BlueZ 1/3] client/btpclient: refactor read-commands bitmap building Frédéric Danis
2026-05-19 12:34 ` client/btpclient: Add GAP extended advertising support bluez.test.bot
2026-05-19 10:55 ` [PATCH BlueZ 2/3] client/btpclient: Replace advertising defines by shared ones Frédéric Danis
2026-05-19 10:55 ` [PATCH BlueZ 3/3] client/btpclient: Add BTP_OP_GAP_SET_EXTENDED_ADVERTISING support Frédéric Danis
2026-05-21 13:30 ` [PATCH BlueZ 0/3] client/btpclient: Add GAP extended advertising support patchwork-bot+bluetooth
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=20260519105519.226648-1-frederic.danis@collabora.com \
--to=frederic.danis@collabora.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