From: Kyle Manna <kyle@kylemanna.com>
To: linux-bluetooth@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Kyle Manna <kyle@kylemanna.com>
Subject: [PATCH 0/2] Add support fo BT LE Connection Parameters
Date: Thu, 4 Jul 2013 16:25:01 -0700 [thread overview]
Message-ID: <1372980303-3007-1-git-send-email-kyle@kylemanna.com> (raw)
This patch series adds support for calling setsockopt() on a l2cap socket to set connection parameters prior to calling connect().
The motivation for setting the paremeters prior to connect is to:
1) Reduce the issues caused with BT and WiFi hardware radios that share the same antenna. During the connection, typically the WiFi portion of the radio is blocked. Setting the connection parameters such as the window and interval allow the userspace app to tune and compromise.
2) Eliminate the need to call HCI connection update when the paremeters are known ahead of time.
Kyle Manna (2):
bluetooth: Pass HCI LE connection parameters
bluetooth: Add l2cap sockopt for LE conn params
include/net/bluetooth/bluetooth.h | 2 ++
include/net/bluetooth/hci_core.h | 5 +++--
include/net/bluetooth/l2cap.h | 2 ++
net/bluetooth/hci_conn.c | 33 ++++++++++++++-------------------
net/bluetooth/l2cap_core.c | 13 +++++++++++--
net/bluetooth/l2cap_sock.c | 25 +++++++++++++++++++++++++
net/bluetooth/mgmt.c | 4 ++--
net/bluetooth/sco.c | 2 +-
8 files changed, 60 insertions(+), 26 deletions(-)
--
1.8.1.2
next reply other threads:[~2013-07-04 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 23:25 Kyle Manna [this message]
2013-07-04 23:25 ` [PATCH 1/2] bluetooth: Pass HCI LE connection parameters Kyle Manna
2013-07-04 23:25 ` [PATCH 2/2] bluetooth: Add l2cap sockopt for LE conn params Kyle Manna
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=1372980303-3007-1-git-send-email-kyle@kylemanna.com \
--to=kyle@kylemanna.com \
--cc=davem@davemloft.net \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@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).