linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brennan Ashton <brn@deako.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: Option to disable filtering of duplicate LE ADV
Date: Mon, 12 Sep 2016 09:42:01 -0700	[thread overview]
Message-ID: <1473698521.3306.4.camel@deako.com> (raw)
In-Reply-To: <CABBYNZLkY1mQ8m62oWw1gFLrLVVOj_ENUuxCaLhwZnAbE4eB+g@mail.gmail.com>

On Mon, 2016-09-12 at 13:52 +0300, Luiz Augusto von Dentz wrote:
> Hi Marcel, Johan,
> 
> On Mon, Sep 12, 2016 at 9:47 AM, Marcel Holtmann <marcel@holtmann.org
> > wrote:
> > 
> > Hi Johan,
> > 
> > > 
> > > > 
> > > > > 
> > > > > Right now in all of the le_scan functions filter_dup is set
> > > > > to
> > > > > LE_SCAN_FILTER_DUP_ENABLE.  This is not always desired with
> > > > > beacons as
> > > > > the content may change.  I can force this by sending the HCI
> > > > > commands
> > > > > to enable scanning without this filter, but then the mgmt api
> > > > > (and
> > > > > DBUS) cannot be used for scanning.
> > > > > 
> > > > > I was wondering if people had thoughts on making this
> > > > > configurable?
> > > > 
> > > > Check out the SetDiscoveryFilter:
> > > > 
> > > > https://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/adapte
> > > > r-api.txt
> > > > 
> > > > When that is used it will not enable duplicated filter and in
> > > > fact is
> > > > the only way to discover beacons which don't have discoverable
> > > > flags
> > > > sets e.g. broadcaster.
> > > 
> > > Actually Brennan is right that none of these methods disable
> > > duplicate
> > > filtering. All of the places in the kernel that set the LE scan
> > > parameters explicitly enable duplicate filtering. I suppose we
> > > should
> > > seriously consider extending the mgmt API to allow performing LE
> > > scan
> > > without the duplicate filtering. Right now the only way to do
> > > that is
> > > through raw HCI access.
> > 
> > however when a driver sets the strict duplicate filtering quirk,
> > then scanning will be restarted and thus new advertising data can
> > be found.
> 
> Im not sure what the quirk actually means but it doesn't look like it
> will be able to attend the RSSI filtering since the controller may
> omit results thus why I though duplicate was not enabled when
> filtering is. From the code it looks like the quirk would force
> restarting the scanning:
> 
> /* If duplicate filtering does not report RSSI changes, then restart
> * scanning to ensure updated result with updated RSSI values.
> */
> if (test_bit(HCI_QUIRK_STRICT_DUPLICATE_FILTER, &hdev->quirks)) {
> restart_le_scan(hdev);
> 
> Isn't that a causing a little too many restarts? I wonder if there is
> anyone using this quirk in practice? And is this really worth it
> instead of just disabling the duplicate filter?
> 

I am not sure I fully understand what this quirk, but I suspect we are
going to want to have the option for turning on duplicate filtering.
Beacons and mesh are going to become more and more common and the later
would cause an HCI event every time a new packet was broadcast. In most
cases these are not of interest to people unless they are explicity
expecting them.

I would propose adding SetSuplicateFilter to the adaptor API. I am
happy to write some code for this today if people think this makes
sense.


--Brennan

      reply	other threads:[~2016-09-12 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 20:00 Option to disable filtering of duplicate LE ADV Brennan Ashton
2016-09-10  8:27 ` Luiz Augusto von Dentz
2016-09-10 13:15   ` Johan Hedberg
2016-09-12  6:47     ` Marcel Holtmann
2016-09-12 10:52       ` Luiz Augusto von Dentz
2016-09-12 16:42         ` Brennan Ashton [this message]

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=1473698521.3306.4.camel@deako.com \
    --to=brn@deako.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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).