From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH hcidump 2/2] Add decoding AMP Assoc data in write_remote_amp_assoc
Date: Thu, 19 Jul 2012 12:08:25 +0300 [thread overview]
Message-ID: <1342688905-31924-2-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1342688905-31924-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Use amp_assoc_dump in write_remote_amp_assoc HCI command
---
parser/hci.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/parser/hci.c b/parser/hci.c
index 5b837e9..6ff30e3 100644
--- a/parser/hci.c
+++ b/parser/hci.c
@@ -1657,6 +1657,17 @@ static inline void le_set_scan_enable_dump(int level, struct frame *frm)
(cp->filter_dup == 0x00 ? "disabled" : "enabled"));
}
+static inline void write_remote_amp_assoc_cmd_dump(int level, struct frame *frm)
+{
+ write_remote_amp_assoc_cp *cp = frm->ptr;
+
+ p_indent(level, frm);
+ printf("handle 0x%2.2x len_so_far %d remaining_len %d\n", cp->handle,
+ cp->length_so_far, cp->remaining_length);
+
+ amp_assoc_dump(level + 1, cp->fragment, frm->len - 5);
+}
+
static inline void command_dump(int level, struct frame *frm)
{
hci_command_hdr *hdr = frm->ptr;
@@ -1934,6 +1945,9 @@ static inline void command_dump(int level, struct frame *frm)
case OCF_READ_CLOCK:
request_clock_dump(level + 1, frm);
return;
+ case OCF_WRITE_REMOTE_AMP_ASSOC:
+ write_remote_amp_assoc_cmd_dump(level + 1, frm);
+ return;
}
break;
--
1.7.9.5
next prev parent reply other threads:[~2012-07-19 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 9:08 [PATCH hcidump 1/2] lib: Correct length name in write assoc struct Andrei Emeltchenko
2012-07-19 9:08 ` Andrei Emeltchenko [this message]
2012-07-19 12:16 ` Johan Hedberg
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=1342688905-31924-2-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=andrei.emeltchenko.news@gmail.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;
as well as URLs for NNTP newsgroup(s).