From: "Pali Rohár" <pali@kernel.org>
To: linux-bluetooth@vger.kernel.org
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Subject: [PATCH] avinfo: Print more A/V capabilities
Date: Tue, 12 May 2020 18:51:12 +0200 [thread overview]
Message-ID: <20200512165112.24006-1-pali@kernel.org> (raw)
---
tools/avinfo.c | 27 ++++++++++++++++++++++++---
1 file changed, 24 insertions(+), 3 deletions(-)
diff --git a/tools/avinfo.c b/tools/avinfo.c
index e45b50918..576981a5e 100644
--- a/tools/avinfo.c
+++ b/tools/avinfo.c
@@ -65,6 +65,7 @@
#define AVDTP_HEADER_COMPRESSION 0x05
#define AVDTP_MULTIPLEXING 0x06
#define AVDTP_MEDIA_CODEC 0x07
+#define AVDTP_DELAY_REPORTING 0x08
/* SEP types definitions */
#define AVDTP_SEP_TYPE_SOURCE 0x00
@@ -696,13 +697,33 @@ static void print_caps(void *data, int size)
switch (cap->category) {
case AVDTP_MEDIA_TRANSPORT:
+ printf("\tMedia Transport: Supported\n");
+ break;
case AVDTP_REPORTING:
+ printf("\tReporting: Supported\n");
+ break;
+ case AVDTP_DELAY_REPORTING:
+ printf("\tDelay Reporting: Supported\n");
+ break;
case AVDTP_RECOVERY:
+ case AVDTP_HEADER_COMPRESSION:
case AVDTP_MULTIPLEXING:
- /* FIXME: Add proper functions */
- break;
default:
- printf("\tUnknown category: %d\n", cap->category);
+ switch (cap->category) {
+ case AVDTP_RECOVERY:
+ printf("\tRecovery:\n");
+ break;
+ case AVDTP_HEADER_COMPRESSION:
+ printf("\tHeader compression:\n");
+ break;
+ case AVDTP_MULTIPLEXING:
+ printf("\tMultiplexing:\n");
+ break;
+ default:
+ printf("\tUnknown category: %d\n", cap->category);
+ break;
+ }
+ /* FIXME: Add proper functions */
printf("\t\tData:");
for (i = 0; i < cap->length; ++i)
printf(" 0x%.02x",
--
2.20.1
next reply other threads:[~2020-05-12 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:51 Pali Rohár [this message]
2020-05-12 17:37 ` avinfo: Print more A/V capabilities bluez.test.bot
2020-05-12 17:37 ` bluez.test.bot
2020-07-01 8:35 ` [PATCH] " Pali Rohár
2020-08-08 13:23 ` Pali Rohár
2020-09-29 21:34 ` Pali Rohár
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=20200512165112.24006-1-pali@kernel.org \
--to=pali@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.