linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Petri Gynther <pgynther@google.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: BlueZ 5.43: HoG peripheral services re-discovered again and again on every reconnect
Date: Fri, 2 Dec 2016 13:56:10 +0200	[thread overview]
Message-ID: <CABBYNZKQ5nA2wr-9AeiGyBDoDiwdiABoTDLQtwv7cZgPMvBSWw@mail.gmail.com> (raw)
In-Reply-To: <CAGXr9JGXtwsMxfZd-VKNAtWa3M13oYBacxb7RW-skF5b7S1+1Q@mail.gmail.com>

Hi Petri,

On Thu, Dec 1, 2016 at 11:12 PM, Petri Gynther <pgynther@google.com> wrote:
> However, in this case, I think this handling is correct.
> load_gatt_db() showed "No cache for LEFQAU", so BlueZ has to
> re-discover everything from the device over BLE.
> But, since the device disconnected in the middle of discovery, BlueZ
> couldn't fully populate the GATT DB and has to clean it.
> If the device didn't disconnect so quickly, this would have most likely worked.
>
>> But I do agree that we should not reset the db if that was populated
>> already, so I will try to fix that.
>
> Yes, once BlueZ does not reset the GATT DB on failed reconnects, this
> problem will be solved.

Please check if everything is alright when using upstream, it should
clear the database anymore if we get an early disconnect.


-- 
Luiz Augusto von Dentz

  reply	other threads:[~2016-12-02 11:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 19:39 BlueZ 5.43: HoG peripheral services re-discovered again and again on every reconnect Petri Gynther
2016-11-10 14:17 ` Luiz Augusto von Dentz
2016-11-11  2:42   ` Petri Gynther
2016-11-11  9:07     ` Luiz Augusto von Dentz
     [not found]       ` <CAGXr9JET_-mB1qtOryXpUMhQPTe_ecw84f4kFH+Wv9_WYp3iog@mail.gmail.com>
2016-11-29 23:15         ` Petri Gynther
2016-11-30  8:36           ` Luiz Augusto von Dentz
2016-11-30  9:37             ` Luiz Augusto von Dentz
2016-11-30 22:15               ` Petri Gynther
2016-11-30 22:55                 ` Petri Gynther
2016-12-01  7:54                   ` Luiz Augusto von Dentz
2016-12-01  8:21                 ` Luiz Augusto von Dentz
2016-12-01 21:12                   ` Petri Gynther
2016-12-02 11:56                     ` Luiz Augusto von Dentz [this message]
2016-12-08 21:52                       ` Petri Gynther
2016-12-09  8:43                         ` José Bollo
2016-12-09 17:38                           ` Petri Gynther

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=CABBYNZKQ5nA2wr-9AeiGyBDoDiwdiABoTDLQtwv7cZgPMvBSWw@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pgynther@google.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).