From: Marcel Holtmann <marcel@holtmann.org>
To: Andre Guedes <andre.guedes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC v2 1/4] Bluetooth: Prepare start_discovery
Date: Sat, 18 Feb 2012 07:39:42 +0100 [thread overview]
Message-ID: <1329547182.28848.194.camel@aeonflux> (raw)
In-Reply-To: <1329521978-8537-2-git-send-email-andre.guedes@openbossa.org>
Hi Andre,
> This patch does some code refactoring in start_discovery function
> in order to prepare it for interleaved discovery support.
>
> MGMT_ADDR_* macros were moved to hci_core.h since they are now used
> to define discovery type macros.
>
> Discovery type macros were defined according to mgmt-api.txt
> specification:
>
> Possible values for the Type parameter are a bit-wise or of the
> following bits:
>
> 1 BR/EDR
> 2 LE Public
> 3 LE Random
>
> By combining these e.g. the following values are possible:
>
> 1 BR/EDR
> 6 LE (public & random)
> 7 BR/EDR/LE (interleaved discovery)
>
> Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
> ---
> include/net/bluetooth/hci_core.h | 12 ++++++++++++
> include/net/bluetooth/mgmt.h | 5 -----
> net/bluetooth/mgmt.c | 15 ++++++++++-----
> 3 files changed, 22 insertions(+), 10 deletions(-)
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2012-02-18 6:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 23:39 [RFC v2 0/4] MGMT Start Discovery interleaved support Andre Guedes
2012-02-17 23:39 ` [RFC v2 1/4] Bluetooth: Prepare start_discovery Andre Guedes
2012-02-18 6:39 ` Marcel Holtmann [this message]
2012-02-17 23:39 ` [RFC v2 2/4] Bluetooth: Track discovery type Andre Guedes
2012-02-17 23:39 ` [RFC v2 3/4] Bluetooth: Merge INQUIRY and LE_SCAN discovery states Andre Guedes
2012-02-17 23:39 ` [RFC v2 4/4] Bluetooth: Interleaved discovery support Andre Guedes
2012-02-19 10:51 ` [RFC v2 0/4] MGMT Start Discovery interleaved support Johan Hedberg
2012-02-19 13:13 ` Ulisses Furquim
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=1329547182.28848.194.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=andre.guedes@openbossa.org \
--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).