-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'for-upstream' of git://git.kernel.org/pub/scm/linux/ker…
…nel/git/bluetooth/bluetooth-next Johan Hedberg says: ==================== pull request: bluetooth-next 2020-05-13 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. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
- Loading branch information
Showing
23 changed files
with
618 additions
and
258 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
54 changes: 54 additions & 0 deletions
54
Documentation/devicetree/bindings/net/realtek-bluetooth.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
# SPDX-License-Identifier: GPL-2.0 | ||
%YAML 1.2 | ||
--- | ||
$id: http://devicetree.org/schemas/net/realtek-bluetooth.yaml# | ||
$schema: http://devicetree.org/meta-schemas/core.yaml# | ||
|
||
title: RTL8723BS/RTL8723CS/RTL8822CS Bluetooth Device Tree Bindings | ||
|
||
maintainers: | ||
- Vasily Khoruzhick <anarsoul@gmail.com> | ||
- Alistair Francis <alistair@alistair23.me> | ||
|
||
description: | ||
RTL8723CS/RTL8723CS/RTL8822CS is WiFi + BT chip. WiFi part is connected over | ||
SDIO, while BT is connected over serial. It speaks H5 protocol with few | ||
extra commands to upload firmware and change module speed. | ||
|
||
properties: | ||
compatible: | ||
oneOf: | ||
- const: "realtek,rtl8723bs-bt" | ||
- const: "realtek,rtl8723cs-bt" | ||
- const: "realtek,rtl8822cs-bt" | ||
|
||
device-wake-gpios: | ||
maxItems: 1 | ||
description: GPIO specifier, used to wakeup the BT module | ||
|
||
enable-gpios: | ||
maxItems: 1 | ||
description: GPIO specifier, used to enable the BT module | ||
|
||
host-wake-gpios: | ||
maxItems: 1 | ||
description: GPIO specifier, used to wakeup the host processor | ||
|
||
required: | ||
- compatible | ||
|
||
examples: | ||
- | | ||
#include <dt-bindings/gpio/gpio.h> | ||
uart1 { | ||
pinctrl-names = "default"; | ||
pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; | ||
uart-has-rtscts = <1>; | ||
bluetooth { | ||
compatible = "realtek,rtl8723bs-bt"; | ||
device-wake-gpios = <&r_pio 0 5 GPIO_ACTIVE_HIGH>; /* PL5 */ | ||
host-wakeup-gpios = <&r_pio 0 6 GPIO_ACTIVE_HIGH>; /* PL6 */ | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.