linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Batyiev <batyiev@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: Temporary device removal during discovery
Date: Thu, 9 Jul 2020 01:57:06 +0300	[thread overview]
Message-ID: <CAEQQxWwzzZoFiGQg7minJU6pLRY=B5-yLSOun+xksZHUAEWgRA@mail.gmail.com> (raw)
In-Reply-To: <CABBYNZLzQH5ow02xB61d8pF7pcxXoP7Boa06G-HNxJ0Q66FGRg@mail.gmail.com>

Hi Luiz,

On Thu, Jul 9, 2020 at 12:14 AM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
> The delta logic might be a nice addition as a separate patch, it is
> more for detecting devices disappearing then actually cleanup during
> power off.
No-no, it's not about adapter powering off.

I meant that (external) devices never disappear from the bluez device
list during the discovery,
even if the (external) devices are turned off (i.e. they should be
purged by bluez).

So:
- bluez is central
- bluez is discovering
- peripheral appear for a moment, than disappear (i.e. peripheral
would be turned off)
- bluez would not remove device from the list (at least until
discovery is stopped)

Use case:
- bluez is monitoring environment (discovering literally forever)
- peripherals are brought in and out of bluez visibility range
- bluez list of visible devices grows infinitely and causes problems
(hundreds of devices)


Thanks,
   Andrey

  parent reply	other threads:[~2020-07-08 22:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 10:24 Temporary device removal during discovery Andrey Batyiev
2020-07-08 11:29 ` Bastien Nocera
2020-07-08 15:53   ` Andrey Batyiev
2020-07-08 21:14     ` Luiz Augusto von Dentz
2020-07-08 21:19       ` Luiz Augusto von Dentz
2020-07-08 22:57       ` Andrey Batyiev [this message]
2020-07-09  0:13         ` Luiz Augusto von Dentz
2020-07-09  8:26         ` Bastien Nocera
2020-07-10 18:06           ` Luiz Augusto von Dentz
2020-07-10 19:00             ` Bastien Nocera
2020-07-10 20:27               ` Luiz Augusto von Dentz

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='CAEQQxWwzzZoFiGQg7minJU6pLRY=B5-yLSOun+xksZHUAEWgRA@mail.gmail.com' \
    --to=batyiev@gmail.com \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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).