From: Johan Hedberg <johan.hedberg@gmail.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: pull request: bluetooth-next 2020-05-13
Date: Wed, 13 May 2020 11:15:17 +0300 [thread overview]
Message-ID: <20200513081517.GA35645@isister-mobl.amr.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5422 bytes --]
Hi,
Here's a second attempt at a bluetooth-next pull request which
supercedes the one dated 2020-05-09. This should have the issues
discovered by Jakub fixed.
- Add support for Intel Typhoon Peak device (8087:0032)
- Add device tree bindings for Realtek RTL8723BS device
- Add device tree bindings for Qualcomm QCA9377 device
- Add support for experimental features configuration through mgmt
- Add driver hook to prevent wake from suspend
- Add support for waiting for L2CAP disconnection response
- Multiple fixes & cleanups to the btbcm driver
- Add support for LE scatternet topology for selected devices
- A few other smaller fixes & cleanups
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 44dd5efc97dae0dc09ea9316597826c8b0fd1578:
Merge branch 'Support-programmable-pins-for-Ocelot-PTP-driver' (2020-04-21 15:38:34 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git for-upstream
for you to fetch changes up to 5b440676c15bbe1a40f2546ec92db83ed66d9e22:
Bluetooth: L2CAP: add support for waiting disconnection resp (2020-05-13 10:03:51 +0200)
----------------------------------------------------------------
Abhishek Pandit-Subedi (5):
Bluetooth: Fix incorrect type for window and interval
Bluetooth: Modify LE window and interval for suspend
Bluetooth: Rename BT_SUSPEND_COMPLETE
Bluetooth: Add hook for driver to prevent wake from suspend
Bluetooth: btusb: Implement hdev->prevent_wake
Alain Michaud (3):
Bluetooth: Adding driver and quirk defs for multi-role LE
Bluetooth: allow scatternet connections if supported.
Bluetooth: btusb: Adding support for LE scatternet to Jfp and ThP
Archie Pusaka (1):
Bluetooth: L2CAP: add support for waiting disconnection resp
Christian Hewitt (3):
dt-bindings: net: bluetooth: Add device tree bindings for QCA9377
Bluetooth: hci_qca: add compatible for QCA9377
Bluetooth: hci_qca: allow max-speed to be set for QCA9377 devices
Hans de Goede (8):
Bluetooth: btbcm: Drop upper nibble version check from btbcm_initialize()
Bluetooth: btbcm: Move setting of USE_BDADDR_PROPERTY quirk to hci_bcm.c
Bluetooth: btbcm: Fold Patch loading + applying into btbcm_initialize()
Bluetooth: btbcm: Make btbcm_initialize() print local-name on re-init too
Bluetooth: btbcm: Make btbcm_setup_patchram use btbcm_finalize
Bluetooth: btbcm: Bail sooner from btbcm_initialize() when not loading fw
Bluetooth: btbcm: Try multiple Patch filenames when loading the Patch firmware
Bluetooth: btbcm: Add 2 missing models to subver tables
Konstantin Forostyan (1):
Bluetooth: L2CAP: Fix errors during L2CAP_CREDIT_BASED_CONNECTION_REQ (0x17)
Marcel Holtmann (7):
Bluetooth: Add MGMT_EV_PHY_CONFIGURATION_CHANGED to supported list
Bluetooth: Replace BT_DBG with bt_dev_dbg for management support
Bluetooth: replace zero-length array with flexible-array member
Bluetooth: Introduce HCI_MGMT_HDEV_OPTIONAL option
Bluetooth: Replace BT_DBG with bt_dev_dbg for security manager support
Bluetooth: Add support for experimental features configuration
Bluetooth: Introduce debug feature when dynamic debug is disabled
Raghuram Hegde (1):
Bluetooth: btusb: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)
Rikard Falkeborn (1):
Bluetooth: serdev: Constify serdev_device_ops
Sonny Sasaka (1):
Bluetooth: Handle Inquiry Cancel error after Inquiry Complete
Tedd Ho-Jeong An (1):
Bluetooth: Fix advertising handle is set to 0
Vasily Khoruzhick (2):
dt-bindings: net: bluetooth: Add rtl8723bs-bluetooth
Bluetooth: hci_h5: Add support for binding RTL8723BS with device tree
.../devicetree/bindings/net/qualcomm-bluetooth.txt | 5 +
.../devicetree/bindings/net/realtek-bluetooth.yaml | 54 +++
drivers/bluetooth/btbcm.c | 139 ++++----
drivers/bluetooth/btbcm.h | 10 +-
drivers/bluetooth/btusb.c | 20 +-
drivers/bluetooth/hci_bcm.c | 27 +-
drivers/bluetooth/hci_h5.c | 2 +
drivers/bluetooth/hci_qca.c | 17 +-
drivers/bluetooth/hci_serdev.c | 4 +-
include/net/bluetooth/bluetooth.h | 11 +
include/net/bluetooth/hci.h | 10 +
include/net/bluetooth/hci_core.h | 4 +-
include/net/bluetooth/mgmt.h | 69 ++--
net/bluetooth/Kconfig | 7 +
net/bluetooth/hci_core.c | 8 +-
net/bluetooth/hci_event.c | 23 +-
net/bluetooth/hci_request.c | 12 +-
net/bluetooth/hci_sock.c | 12 +-
net/bluetooth/l2cap_core.c | 4 +-
net/bluetooth/l2cap_sock.c | 30 +-
net/bluetooth/lib.c | 33 ++
net/bluetooth/mgmt.c | 367 ++++++++++++++-------
net/bluetooth/smp.c | 8 +-
23 files changed, 618 insertions(+), 258 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/realtek-bluetooth.yaml
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2020-05-13 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 8:15 Johan Hedberg [this message]
2020-05-13 19:21 ` pull request: bluetooth-next 2020-05-13 David Miller
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=20200513081517.GA35645@isister-mobl.amr.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.