From: Daniel Winkler <danielwinkler@google.com>
To: linux-bluetooth@vger.kernel.org
Cc: chromeos-bluetooth-upstreaming@chromium.org,
Daniel Winkler <danielwinkler@google.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH 0/2] Bluetooth: Report extended adv capabilities to userspace
Date: Tue, 25 Aug 2020 16:31:49 -0700 [thread overview]
Message-ID: <20200825233151.1580920-1-danielwinkler@google.com> (raw)
Hi Maintainers,
This series improves the kernel/controller support that is reported
to userspace for the following extended advertising features:
1. If extended advertising is available, the number of hardware slots
is used and reported, rather than the fixed default of 5. If no hardware
support is available, default is used as before for software rotation.
2. New flags indicating general hardware offloading and ability to
set tx power level. These are kept as two separate flags because in
the future vendor commands may allow tx power to be set without
hardware offloading support.
Daniel Winkler (2):
bluetooth: Report num supported adv instances for hw offloading
bluetooth: Add MGMT capability flags for tx power and ext advertising
include/net/bluetooth/mgmt.h | 2 ++
net/bluetooth/hci_core.c | 2 +-
net/bluetooth/mgmt.c | 8 +++++---
3 files changed, 8 insertions(+), 4 deletions(-)
--
2.28.0.297.g1956fa8f8d-goog
next reply other threads:[~2020-08-25 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 23:31 Daniel Winkler [this message]
2020-08-25 23:31 ` [PATCH 1/2] bluetooth: Report num supported adv instances for hw offloading Daniel Winkler
2020-08-25 23:31 ` [PATCH 2/2] bluetooth: Add MGMT capability flags for tx power and ext advertising Daniel Winkler
2020-09-11 7:18 ` [PATCH 0/2] Bluetooth: Report extended adv capabilities to userspace Marcel Holtmann
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=20200825233151.1580920-1-danielwinkler@google.com \
--to=danielwinkler@google.com \
--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=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
all inboxes | Powered by JetHome®