Linux bluetooth development
 help / color / mirror / Atom feed
From: Mikel Astiz <mikel.astiz.oss@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: [RFC v1 0/7] One remote UUID per btd_profile
Date: Wed,  6 Feb 2013 10:16:20 +0100	[thread overview]
Message-ID: <1360142187-15347-1-git-send-email-mikel.astiz.oss@gmail.com> (raw)

From: Mikel Astiz <mikel.astiz@bmw-carit.de>

There was no feedback for v0, and therefore I resubmit this patchset rebased and with the following main changes:

- AVRCP gets split but both roles share a common config in audio.conf
- Health profile also split into two profiles (patch v1 6/7)
- Core simplified by limiting to one UUID per btd_profile (patch v1 7/7)

There's a lot more that code be simplified after 7/7 but this has been left aside for the moment.

>From original cover-letter:

Disclaimer: this RFC is WIP and hasn't been tested, specially because I don't have the necessary hardware for it.

The goal is to have one remote_uuid per btd_profile. There are only a few exceptions to this rule, and this patchset tries to fix three of them. This basically means splitting one btd_profile per role.

Mikel Astiz (7):
  avrcp: Refactor server registration
  audio: Split AVRCP into two btd_profile
  proximity: Split internal monitor registration API
  proximity: Split monitor into three btd_profile
  gatt: List only GATT_UUID as remote UUID
  health: Split health into two btd_profile
  profile: Limit to one remote UUID per profile

 profiles/audio/avrcp.c               | 114 +++++++++++++-----
 profiles/audio/avrcp.h               |   6 +-
 profiles/audio/manager.c             |  75 ++++++++----
 profiles/cyclingspeed/cyclingspeed.c |   2 +-
 profiles/deviceinfo/deviceinfo.c     |   2 +-
 profiles/gatt/gas.c                  |   2 +-
 profiles/health/hdp_manager.c        |  20 +++-
 profiles/heartrate/heartrate.c       |   2 +-
 profiles/input/hog.c                 |   2 +-
 profiles/input/manager.c             |   2 +-
 profiles/network/manager.c           |   6 +-
 profiles/proximity/manager.c         | 100 ++++++++++++----
 profiles/proximity/monitor.c         | 220 ++++++++++++++++++++++++++++-------
 profiles/proximity/monitor.h         |  17 ++-
 profiles/scanparam/scan.c            |   2 +-
 profiles/thermometer/thermometer.c   |   2 +-
 src/device.c                         |  49 +++-----
 src/profile.c                        |  25 ++--
 src/profile.h                        |   4 +-
 19 files changed, 466 insertions(+), 186 deletions(-)

-- 
1.8.1


             reply	other threads:[~2013-02-06  9:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06  9:16 Mikel Astiz [this message]
2013-02-06  9:16 ` [RFC v1 1/7] avrcp: Refactor server registration Mikel Astiz
2013-02-06  9:16 ` [RFC v1 2/7] audio: Split AVRCP into two btd_profile Mikel Astiz
2013-02-07  9:43   ` Luiz Augusto von Dentz
2013-02-07 10:43     ` Mikel Astiz
2013-02-06  9:16 ` [RFC v1 3/7] proximity: Split internal monitor registration API Mikel Astiz
2013-02-14 16:37   ` Claudio Takahasi
2013-02-15  7:54     ` Mikel Astiz
2013-02-27  7:46       ` Mikel Astiz
2013-02-28 19:34       ` Claudio Takahasi
2013-02-06  9:16 ` [RFC v1 4/7] proximity: Split monitor into three btd_profile Mikel Astiz
2013-02-06  9:16 ` [RFC v1 5/7] gatt: List only GATT_UUID as remote UUID Mikel Astiz
2013-02-06  9:16 ` [RFC v1 6/7] health: Split health into two btd_profile Mikel Astiz
2013-02-06  9:16 ` [RFC v1 7/7] profile: Limit to one remote UUID per profile Mikel Astiz

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=1360142187-15347-1-git-send-email-mikel.astiz.oss@gmail.com \
    --to=mikel.astiz.oss@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mikel.astiz@bmw-carit.de \
    /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