From: Jaganath Kanakkassery <jaganath.k.os@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Jaganath Kanakkassery <jaganathx.kanakkassery@intel.com>
Subject: [PATCH 2/3 v2] doc/mgmt-api: Add support for Set default Phy command
Date: Mon, 20 Nov 2017 15:56:56 +0530 [thread overview]
Message-ID: <1511173617-25442-3-git-send-email-jaganathx.kanakkassery@intel.com> (raw)
In-Reply-To: <1511173617-25442-1-git-send-email-jaganathx.kanakkassery@intel.com>
---
doc/mgmt-api.txt | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index 69e84cd..b59bf0c 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -2940,9 +2940,47 @@ Get PHY Information Command
LE 1M TX and LE 1M RX would be supported by default.
This command is only available for LE capable controllers.
+ It will return Not Supported otherwise.
+
+ Possible errors: Not Supported
+ Invalid Index
+
+Set Default PHY Command
+==========================
+
+ Command Code: 0x0044
+ Controller Index: <controller id>
+ Command Parameters: Default_phy (1 Octet)
+ Return Parameters: Current_phys (1 Octet)
+
+ This command is used to set the default PHYs to the controller.
+
+ This will be stored and used for all the subsequent scanning
+ and connection initiation.
+
+ Prior to this, Get PHY information Command should be called
+ to retrieve the supported PHYs by the controller. If default_phy
+ has PHY not supported by the controller (not there in supported_phys)
+ then Invalid Parameters will be returned.
+
+ This can be called at any point to change the preferred PHYs.
+
+ Default_phy is a bitmask with the following bits.
+ 0 LE 1M TX
+ 1 LE 1M RX
+ 2 LE 2M TX
+ 3 LE 2M RX
+ 4 LE CODED TX
+ 5 LE CODED RX
+
+ This command generates a Command Complete event on success
+ or a Command Status event on failure.
+
+ This command is only available for LE capable controllers.
It will return Not Supported otherwise.
Possible errors: Not Supported
+ Invalid Parameters
Invalid Index
Command Complete Event
--
2.7.4
next prev parent reply other threads:[~2017-11-20 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 10:26 [PATCH 0/3 v2] LE New PHYs kernel interfaces Jaganath Kanakkassery
2017-11-20 10:26 ` [PATCH 1/3 v2] doc/mgmt-api: Add support for Get PHY information command Jaganath Kanakkassery
2017-11-27 13:39 ` Johan Hedberg
2017-11-27 14:56 ` Jaganath K
2017-11-28 8:39 ` Marcel Holtmann
2017-11-20 10:26 ` Jaganath Kanakkassery [this message]
2017-11-28 8:56 ` [PATCH 2/3 v2] doc/mgmt-api: Add support for Set default Phy command Marcel Holtmann
2017-11-28 11:39 ` Jaganath K
2017-11-28 11:50 ` Marcel Holtmann
2017-11-20 10:26 ` [PATCH 3/3 v2] doc/mgmt-api: Add advertising phys support to flags Jaganath Kanakkassery
2017-11-27 13:32 ` Johan Hedberg
2017-11-27 14:42 ` Jaganath K
2017-11-28 7:43 ` Marcel Holtmann
2017-11-28 9:28 ` Jaganath K
2017-11-28 10:22 ` Marcel Holtmann
2017-11-27 10:51 ` [PATCH 0/3 v2] LE New PHYs kernel interfaces Jaganath K
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=1511173617-25442-3-git-send-email-jaganathx.kanakkassery@intel.com \
--to=jaganath.k.os@gmail.com \
--cc=jaganathx.kanakkassery@intel.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).