From: Jaganath Kanakkassery <jaganath.k.os@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Jaganath Kanakkassery <jaganathx.kanakkassery@intel.com>
Subject: [PATCH 0/3 v2] LE New PHYs kernel interfaces
Date: Mon, 20 Nov 2017 15:56:54 +0530 [thread overview]
Message-ID: <1511173617-25442-1-git-send-email-jaganathx.kanakkassery@intel.com> (raw)
These patches enables user to get the supported phys by the
controller and set preferred phy to be used in subsequent
scanning and connection initiation.
Also added flags to support user selection for phy to be
advertised.
v1: Applied Marcel's comments
v2: Applied Eramoto's comments
Jaganath Kanakkassery (3):
doc/mgmt-api: Add support for Get PHY information command
doc/mgmt-api: Add support for Set default Phy command
doc/mgmt-api: Add advertising phys support to flags
doc/mgmt-api.txt | 88 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 88 insertions(+)
--
2.7.4
next 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 Jaganath Kanakkassery [this message]
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 ` [PATCH 2/3 v2] doc/mgmt-api: Add support for Set default Phy command Jaganath Kanakkassery
2017-11-28 8:56 ` 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-1-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).