From: Marcel Holtmann <marcel@holtmann.org>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH] doc: Describe the new debug keys command and setting
Date: Fri, 31 Jan 2014 12:19:28 -0800 [thread overview]
Message-ID: <1391199568-55855-1-git-send-email-marcel@holtmann.org> (raw)
---
doc/mgmt-api.txt | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index 44ff12676180..a32237ae26b3 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -212,6 +212,7 @@ Read Controller Information Command
10 Low Energy
11 Advertising
12 Secure Connections
+ 13 Debug Keys
This command generates a Command Complete event on success or
a Command Status event on failure.
@@ -1423,6 +1424,28 @@ Set Secure Connections Command
Invalid Index
+Set Debug Keys Command
+======================
+
+ Command Code: 0x002E
+ Controller Index: <controller id>
+ Command Parameters: Debug_Keys (1 Octet)
+ Return Parameters: Current_Settings (4 Octets)
+
+ This command is used to tell the kernel whether to accept the
+ usage of debug keys or not. The allowed values for this parameter
+ are 0x00 and 0x01. All other values will return an Invalid Parameters
+ response.
+
+ This command generates a Command Complete event on success or
+ a Command Status event on failure.
+
+ Possible errors: Busy
+ Not Supported
+ Invalid Parameters
+ Invalid Index
+
+
Command Complete Event
======================
--
1.8.5.3
next reply other threads:[~2014-01-31 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 20:19 Marcel Holtmann [this message]
2014-02-02 1:50 ` [PATCH] doc: Describe the new debug keys command and setting 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=1391199568-55855-1-git-send-email-marcel@holtmann.org \
--to=marcel@holtmann.org \
--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