From: Yunhan Wang <yunhanw@nestlabs.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
Martin Turon <mturon@google.com>
Subject: Re: BLE advertisement re-enabling after ble connection goes away
Date: Thu, 13 Dec 2018 13:38:19 -0800 [thread overview]
Message-ID: <CALvjcs9iYvgxN4YWzirw_Fxx30cDKYCyir+ZmpgsuBvcTJN+Zg@mail.gmail.com> (raw)
In-Reply-To: <CALvjcs9zQ3v9pW6_Sy-VJD4hiX2FDrnqV7xYUNkNGg6mVaoHKQ@mail.gmail.com>
+Martin
Hi, Luiz and Marcel
When I take a look at the bluetooth code, it seems it is re-enabling
ble advertisement after ble connection goes away. Any idea?
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/tree/net/bluetooth/hci_event.c#n2634
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/tree/net/bluetooth/hci_event.c#n2712
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/tree/net/bluetooth/hci_request.c#n1386
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/tree/net/bluetooth/hci_request.c#n1734
Thanks
Best wishes
Yunhan
On Wed, Dec 5, 2018 at 6:54 PM Yunhan Wang <yunhanw@nestlabs.com> wrote:
>
> Hi, Luiz and Marcel
>
> May I have a question on ble behavior on BLE re-advertisement?
>
> According to Bluetooth spec Vol. 3 (the host volume), 9.2.4.2, "The
> device shall remain in general discoverable mode until a connection is
> established or the Host terminates the mode."
>
> There is no description on re-enabling the advertising "after"
> disconnection, so the responsibility for re-enabling the advertising
> is bluez or kernel or application code? In other words, does kernel or
> bluez or application would re-enable the ble advertisement after ble
> disconnection happens?
>
> Thanks
> Best wishes
> Yunhan.
next prev parent reply other threads:[~2018-12-13 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 2:54 BLE advertisement re-enabling after ble connection goes away Yunhan Wang
2018-12-13 21:38 ` Yunhan Wang [this message]
[not found] ` <CABBYNZLPeHRWcG78USDYHL6zzw392JuefRaD9S_+RuXhDQ9ZCw@mail.gmail.com>
[not found] ` <CAOOu1=BiJ9VjiMXiiPuXb=4cu-62OYmT+h1Z83ip440KwSpeAw@mail.gmail.com>
2018-12-13 23:10 ` Yunhan Wang
2018-12-13 23:13 ` Yunhan Wang
2018-12-14 1:21 ` Luiz Augusto von Dentz
2018-12-14 2:06 ` Yunhan Wang
2018-12-14 2:32 ` Luiz Augusto von Dentz
2018-12-14 3:08 ` Yunhan Wang
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=CALvjcs9iYvgxN4YWzirw_Fxx30cDKYCyir+ZmpgsuBvcTJN+Zg@mail.gmail.com \
--to=yunhanw@nestlabs.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mturon@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).