From: Archie Pusaka <apusaka@google.com>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>
Cc: CrosBT Upstreaming <chromeos-bluetooth-upstreaming@chromium.org>,
Archie Pusaka <apusaka@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH v3 0/5] MSFT offloading support for advertisement monitor
Date: Wed, 16 Dec 2020 12:33:30 +0800 [thread overview]
Message-ID: <20201216043335.2185278-1-apusaka@google.com> (raw)
From: Archie Pusaka <apusaka@chromium.org>
Hi linux-bluetooth,
This series of patches manages the hardware offloading part of MSFT
extension API. The full documentation can be accessed by this link:
https://docs.microsoft.com/en-us/windows-hardware/drivers/bluetooth/microsoft-defined-bluetooth-hci-commands-and-events
Only four of the HCI commands are planned to be implemented:
HCI_VS_MSFT_Read_Supported_Features (implemented in previous patch),
HCI_VS_MSFT_LE_Monitor_Advertisement,
HCI_VS_MSFT_LE_Cancel_Monitor_Advertisement, and
HCI_VS_MSFT_LE_Set_Advertisement_Filter_Enable.
These are the commands which would be used for advertisement monitor
feature. Only if the controller supports the MSFT extension would
these commands be sent. Otherwise, software-based monitoring would be
performed in the user space instead.
Thanks in advance for your feedback!
Archie
Changes in v3:
* Flips the order of rssi and pattern_count on mgmt struct
* Fix return type of msft_remove_monitor
Changes in v2:
* Add a new opcode instead of modifying an existing one
* Also implement the new MGMT opcode and merge the functionality with
the old one.
Archie Pusaka (5):
Bluetooth: advmon offload MSFT add rssi support
Bluetooth: advmon offload MSFT add monitor
Bluetooth: advmon offload MSFT remove monitor
Bluetooth: advmon offload MSFT handle controller reset
Bluetooth: advmon offload MSFT handle filter enablement
include/net/bluetooth/hci_core.h | 34 ++-
include/net/bluetooth/mgmt.h | 16 ++
net/bluetooth/hci_core.c | 173 +++++++++---
net/bluetooth/mgmt.c | 333 ++++++++++++++++------
net/bluetooth/msft.c | 456 ++++++++++++++++++++++++++++++-
net/bluetooth/msft.h | 27 ++
6 files changed, 919 insertions(+), 120 deletions(-)
--
2.29.2.684.gfbc64c5ab5-goog
next reply other threads:[~2020-12-16 4:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 4:33 Archie Pusaka [this message]
2020-12-16 4:33 ` [PATCH v3 1/5] Bluetooth: advmon offload MSFT add rssi support Archie Pusaka
2020-12-21 9:05 ` Marcel Holtmann
2020-12-16 4:33 ` [PATCH v3 2/5] Bluetooth: advmon offload MSFT add monitor Archie Pusaka
2020-12-21 9:09 ` Marcel Holtmann
2020-12-16 4:33 ` [PATCH v3 3/5] Bluetooth: advmon offload MSFT remove monitor Archie Pusaka
2020-12-16 4:33 ` [PATCH v3 4/5] Bluetooth: advmon offload MSFT handle controller reset Archie Pusaka
2020-12-21 9:12 ` Marcel Holtmann
2020-12-22 3:26 ` Archie Pusaka
2020-12-22 10:03 ` Marcel Holtmann
2020-12-22 10:27 ` Archie Pusaka
2020-12-16 4:33 ` [PATCH v3 5/5] Bluetooth: advmon offload MSFT handle filter enablement Archie Pusaka
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=20201216043335.2185278-1-apusaka@google.com \
--to=apusaka@google.com \
--cc=apusaka@chromium.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.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).