From: "Frédéric Danis" <frederic.danis@collabora.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ] doc/qualification: Add PICS and howto for the AVCTP qualification
Date: Tue, 27 Jan 2026 18:05:27 +0100 [thread overview]
Message-ID: <20260127170527.150218-1-frederic.danis@collabora.com> (raw)
---
doc/qualification/avctp-pics.rst | 116 +++++++++++++++++++++++++++++++
doc/qualification/avctp-pts.rst | 49 +++++++++++++
2 files changed, 165 insertions(+)
create mode 100644 doc/qualification/avctp-pics.rst
create mode 100644 doc/qualification/avctp-pts.rst
diff --git a/doc/qualification/avctp-pics.rst b/doc/qualification/avctp-pics.rst
new file mode 100644
index 000000000..6c08d692e
--- /dev/null
+++ b/doc/qualification/avctp-pics.rst
@@ -0,0 +1,116 @@
+.. SPDX-License-Identifier: GPL-2.0-or-later
+.. Copyright © 2025-2026 Collabora Ltd.
+
+======================================
+Audio/Video Control Transport Protocol
+======================================
+(TCRL 2023-1, AVCTP.ICS.1.4.2ed4)
+
+Versions
+========
+**Table 0: X.Y Versions**
+
++------------------+----------+----------------------------------------------+
+| Parameter Name | Selected | Description |
++==================+==========+==============================================+
+| TSPC_AVCTP_0_4 | x | AVCTP 1.4 (M) |
++------------------+----------+----------------------------------------------+
+
+- M: Mandatory
+
+Roles
+=====
+**Table 1: Role Requirements**
+
++------------------+----------+----------------------------------------------+
+| Parameter Name | Selected | Description |
++==================+==========+==============================================+
+| TSPC_AVCTP_1_1 | x | Controller (C.1) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_1_2 | x | Target (C.1) |
++------------------+----------+----------------------------------------------+
+
+- C.1: Mandatory to support at least one.
+
+Controller Capabilities
+=======================
+**Table 2: Controller Features**
+
+Prerequisite: AVCTP 1/1 "Controller"
+
++------------------+----------+----------------------------------------------+
+| Parameter Name | Selected | Description |
++==================+==========+==============================================+
+| TSPC_AVCTP_2_1 | | Message fragmentation (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_2 | x | Transaction label management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_3 | x | Packet type field management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_4 | x | Message type field management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_5 | x | PID field management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_6 | x | IPID field management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_7 | x | Message information management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_8 | x | Event registration for message reception (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_9 | x | Event registration for connection request (O)|
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_10 | x | Event registration for disconnection request |
+| | | (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_11 | x | Connect request (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_12 | x | Disconnect request (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_13 | x | Send message (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_2_14 | | Support for multiple AVCTP channel |
+| | | establishment requests (O) |
++------------------+----------+----------------------------------------------+
+
+- M: Mandatory
+- O: Optional
+
+Target Capabilities
+===================
+**Table 3: Target Features**
+
+Prerequisite: AVCTP 1/2 "Target"
+
++------------------+----------+----------------------------------------------+
+| Parameter Name | Selected | Description |
++==================+==========+==============================================+
+| TSPC_AVCTP_3_1 | | Message fragmentation (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_2 | x | Transaction label management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_3 | x | Packet type field management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_4 | x | Message type field management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_5 | x | PID field management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_6 | x | IPID field management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_7 | x | Message information management (M) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_8 | x | Event registration for message reception (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_9 | x | Event registration for connection request (O)|
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_10 | x | Event registration for disconnection request |
+| | | (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_11 | x | Connect request (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_12 | x | Disconnect request (O) |
++------------------+----------+----------------------------------------------+
+| TSPC_AVCTP_3_13 | x | Send message (O) |
++------------------+----------+----------------------------------------------+
+
+- M: Mandatory
+- O: Optional
diff --git a/doc/qualification/avctp-pts.rst b/doc/qualification/avctp-pts.rst
new file mode 100644
index 000000000..cb47eba0b
--- /dev/null
+++ b/doc/qualification/avctp-pts.rst
@@ -0,0 +1,49 @@
+.. SPDX-License-Identifier: GPL-2.0-or-later
+.. Copyright © 2025-2026 Collabora Ltd.
+
+==================
+AVCTP test results
+==================
+
+:PTS version: 8.5.2 Build 5
+
+Setup
+=====
+
+- Remove PTS device from Bluetooth devices
+
+Tests
+=====
+
+The kernel and BlueZ versions represent the oldest version without backport
+for which we know the test passed.
+
++----------------------+----------+---------+-------+-----------------------+
+| Test name | Result | Kernel | BlueZ | |
++======================+==========+=========+=======+=======================+
+| AVCTP/CT/CCM/BV-01-C | PASS | 6.1 | 5.69 | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/CT/CCM/BV-02-C | PASS | 6.1 | 5.69 | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/CT/CCM/BV-03-C | PASS | 6.1 | 5.69 | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/CT/CCM/BV-04-C | | | | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/CT/NFR/BV-01-C | PASS | 6.1 | 5.69 | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/CT/NFR/BV-04-C | | | | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/TG/CCM/BV-01-C | | | | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/TG/CCM/BV-02-C | | | | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/TG/CCM/BV-03-C | | | | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/TG/CCM/BV-04-C | | | | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/TG/NFR/BI-01-C | PASS | 6.1 | 5.69 | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/TG/NFR/BV-02-C | | | | |
++----------------------+----------+---------+-------+-----------------------+
+| AVCTP/TG/NFR/BV-03-C | | | | |
++----------------------+----------+---------+-------+-----------------------+
--
2.43.0
next reply other threads:[~2026-01-27 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 17:05 Frédéric Danis [this message]
2026-01-27 18:11 ` [BlueZ] doc/qualification: Add PICS and howto for the AVCTP qualification bluez.test.bot
2026-01-27 18:30 ` [PATCH BlueZ] " 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=20260127170527.150218-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