[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4DF7C709-1AD3-42FF-A0C2-EF488D82F083@holtmann.org>
Date: Wed, 18 Mar 2020 12:26:10 +0100
From: Marcel Holtmann <marcel@...tmann.org>
To: Manish Mandlik <mmandlik@...gle.com>
Cc: Yoni Shavit <yshavit@...omium.org>,
Alain Michaud <alainm@...omium.org>,
Miao-chen Chou <mcchou@...omium.org>,
linux-bluetooth@...r.kernel.org,
Dmitry Grinberg <dmitrygr@...gle.com>,
"David S. Miller" <davem@...emloft.net>,
Johan Hedberg <johan.hedberg@...il.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Jakub Kicinski <kuba@...nel.org>
Subject: Re: [PATCH] Bluetooth: Do not cancel advertising when starting a scan
Hi Manish,
> BlueZ cancels adv when starting a scan, but does not cancel a scan when
> starting to adv. Neither is required, so this brings both to a
> consistent state (of not affecting each other). Some very rare (I've
> never seen one) BT 4.0 chips will fail to do both at once. Even this is
> ok since the command that will fail will be the second one, and thus the
> common sense logic of first-come-first-served is preserved for BLE
> requests.
>
> Signed-off-by: Dmitry Grinberg <dmitrygr@...gle.com>
> Signed-off-by: Manish Mandlik <mmandlik@...gle.com>
> ---
>
> net/bluetooth/hci_request.c | 17 -----------------
> 1 file changed, 17 deletions(-)
patch has been applied to bluetooth-next tree.
If you know the controller that doesn’t support this, can we blacklist that one and just disable advertising (peripheral mode) for that controller.
Regards
Marcel
Powered by blists - more mailing lists