linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@codecoup.pl>
To: linux-bluetooth@vger.kernel.org
Cc: Szymon Janc <szymon.janc@codecoup.pl>
Subject: [RFC v2] DeviceLE1 and DeviceBR1 interface
Date: Mon,  4 Apr 2016 03:22:03 +0200	[thread overview]
Message-ID: <1459732924-26643-1-git-send-email-szymon.janc@codecoup.pl> (raw)

Hi,

New proposal with new names: DeviceLE1 and DeviceBR1.
I've also updated interfaces to cover ServicesResolved property.

>From original cover letter:

Current Device1 interface doesn't handle dualmode devices very well and
doesn't provide information if remote supports LE, BR/EDR or both.
There is a problem with bond information, connected transport, supported
technologies etc.

Instead of duplicating properties which would require LE, BR/EDR and
(as currently) mixed variants I propose having two separates interfaces
DeviceSmart1 and DeviceClassic1 which would represent supported transports.

Thanks to this applications can easily track if remote device is LE or not
which is important eg with discovery where different apps can do different
type of discovery or when it want to use profile only over specific
transport.

Eventually those new interfaces would deprecate Device1 interface.

Comments are welcome.

Szymon Janc (1):
  doc: Add DeviceBR1 and DeviceLE1 interfaces

 doc/device-br-api.txt | 200 ++++++++++++++++++++++++++++++++++++++++++++++++++
 doc/device-le-api.txt | 161 ++++++++++++++++++++++++++++++++++++++++
 2 files changed, 361 insertions(+)
 create mode 100644 doc/device-br-api.txt
 create mode 100644 doc/device-le-api.txt

-- 
2.6.2


             reply	other threads:[~2016-04-04  1:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04  1:22 Szymon Janc [this message]
2016-04-04  1:22 ` [RFC v2] doc: Add DeviceBR1 and DeviceLE1 interfaces Szymon Janc
2016-04-05  5:30   ` Johnny Robeson

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=1459732924-26643-1-git-send-email-szymon.janc@codecoup.pl \
    --to=szymon.janc@codecoup.pl \
    --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).