From: Marcel Holtmann <marcel@holtmann.org>
To: Jakub Pawlowski <jpawlowski@google.com>
Cc: Arman Uguray <armansito@chromium.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
Scott James Remnant <keybuk@google.com>
Subject: Re: [RFC] need for new scan api for bluetooth low energy.
Date: Tue, 30 Sep 2014 19:01:50 +0200 [thread overview]
Message-ID: <372D8399-BFC6-413F-924F-44CE79030516@holtmann.org> (raw)
In-Reply-To: <CAD0=r8zcPCWKyTQLQeG68uA21_sEv+5wDKNB-GJzgS1+BcD+bQ@mail.gmail.com>
Hi Jakub,
> ---
> doc/mgmt-api.txt | 69 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 69 insertions(+)
>
> diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
> index 11e2490..1c78f1c 100644
> --- a/doc/mgmt-api.txt
> +++ b/doc/mgmt-api.txt
> @@ -2135,6 +2135,34 @@ Set Public Address Command
> Invalid Index
>
>
> +Start LE Filtered Device Scan
> +=======================
> +
> + Command Code: 0x003A
> + Controller Index: <controller id>
> + Command Parameters: UUID (16 Octets)
> + max_pathloss (1 octet)
> + is_active (1 octet)
> +
> + Return Parameters:
> +
> + This command starts LE scan, and filter received advertisements: if
> AD contains both TX power level and Service Solicitation, and UUID is
> contained in Service Solicitation and computed pathloss is smaller
> than max_pathloss parameter, then a Advertisement Received event will
> be sent.
> +
> + Possible values for the is_active parameter:
> + 0 Start passive scan
> + 1 Start active scan
is really like a one-shot scan? Or is this something you would be running all the time in the background?
Fundamentally if it is one-shot thing then you always want to do active scan, but if it runs in the background then you only want to do passive scanning.
> +
> + This command can only be used when the controller is powered.
> +
> + This command generates a Command Complete event on success or failure.
> +
> + Possible errors: Busy
> + Not Supported
> + Invalid Parameters
> + Not Powered
> + Invalid Index
> +
> +
> Command Complete Event
> ======================
>
> @@ -2851,3 +2879,44 @@ New Configuration Options Event
>
> This event indicates that one or more of the options for the
> controller configuration has changed.
> +
> +
> +Advertisement Received Event
> +==============================
> +
> + Event Code: 0x0020
> + Controller Index: <controller id>
> + Event Parameters: Address (6 Octets)
> + Address_Type (1 Octet)
> + RSSI (1 Octet)
> + Flags (4 Octets)
> + AD_Data_Length (2 Octets)
> + AD_Data (0-65535 Octets)
Device Found event not good enough here? Why would you need a new event with exactly the same parameters?
Regards
Marcel
next prev parent reply other threads:[~2014-09-30 17:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 3:30 [RFC] need for new scan api for bluetooth low energy Jakub Pawlowski
2014-09-17 4:39 ` Marcel Holtmann
2014-09-17 4:52 ` Arman Uguray
2014-09-17 5:14 ` Johan Hedberg
2014-09-17 6:20 ` Jakub Pawlowski
2014-09-17 6:52 ` Johan Hedberg
2014-09-17 7:19 ` Jakub Pawlowski
2014-09-17 7:31 ` Johan Hedberg
2014-09-17 7:44 ` Johan Hedberg
2014-09-17 14:03 ` Marcel Holtmann
2014-09-18 5:58 ` Jakub Pawlowski
2014-09-18 15:37 ` Marcel Holtmann
2014-09-19 16:39 ` Jakub Pawlowski
2014-09-19 16:44 ` Jakub Pawlowski
2014-09-20 1:43 ` Marcel Holtmann
[not found] ` <F673E928-258E-47F7-B71A-F32410974538@holtmann.org>
2014-09-20 4:29 ` Jakub Pawlowski
2014-09-30 16:44 ` Jakub Pawlowski
2014-09-30 17:01 ` Marcel Holtmann [this message]
2014-09-30 17:15 ` Arman Uguray
2014-09-30 17:24 ` Marcel Holtmann
2014-09-30 17:25 ` Jakub Pawlowski
2014-09-30 17:31 ` Marcel Holtmann
2014-09-30 18:29 ` Jakub Pawlowski
2014-09-30 18:54 ` Marcel Holtmann
2014-09-30 21:11 ` Jakub Pawlowski
2014-10-01 5:27 ` Marcel Holtmann
2014-10-10 10:52 ` Marcel Holtmann
2014-10-10 15:49 ` Jakub Pawlowski
2014-10-20 16:55 ` Jakub Pawlowski
2014-10-20 18:22 ` Marcel Holtmann
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=372D8399-BFC6-413F-924F-44CE79030516@holtmann.org \
--to=marcel@holtmann.org \
--cc=armansito@chromium.org \
--cc=jpawlowski@google.com \
--cc=keybuk@google.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