lkml.org 
[lkml]   [2020]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v4 1/2] Bluetooth: btusb: Indicate Microsoft vendor extension for Intel 9460/9560 and 9160/9260
From
Date
Hi Miao-chen,

> This adds a bit mask of driver_info for Microsoft vendor extension and
> indicates the support for Intel 9460/9560 and 9160/9260. See
> https://docs.microsoft.com/en-us/windows-hardware/drivers/bluetooth/
> microsoft-defined-bluetooth-hci-commands-and-events for more information
> about the extension. This also add a kernel config, BT_MSFTEXT, and a
> source file to facilitate Microsoft vendor extension functions.
> This was verified with Intel ThunderPeak BT controller
> where msft_vnd_ext_opcode is 0xFC1E.
>
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
>
> Signed-off-by: Miao-chen Chou <mcchou@chromium.org>
> ---
>
> Changes in v4:
> - Introduce CONFIG_BT_MSFTEXT as a starting point of providing a
> framework to use Microsoft extension
> - Create include/net/bluetooth/msft.h and net/bluetooth/msft.c to
> facilitate functions of Microsoft extension.
>
> Changes in v3:
> - Create net/bluetooth/msft.c with struct msft_vnd_ext defined internally
> and change the hdev->msft_ext field to void*.
> - Define and expose msft_vnd_ext_set_opcode() for btusb use.
> - Init hdev->msft_ext in hci_alloc_dev() and deinit it in hci_free_dev().
>
> Changes in v2:
> - Define struct msft_vnd_ext and add a field of this type to struct
> hci_dev to facilitate the support of Microsoft vendor extension.
>
> drivers/bluetooth/btusb.c | 11 +++++++++--
> include/net/bluetooth/hci_core.h | 4 ++++

so I don’t like the intermixing of core features and drivers unless it is needed. In this case it is not needed since we can first introduce the core support and then enable the driver to use it.

> net/bluetooth/Kconfig | 9 ++++++++-
> net/bluetooth/Makefile | 1 +
> net/bluetooth/msft.c | 16 ++++++++++++++++
> net/bluetooth/msft.h | 19 +++++++++++++++++++
> 6 files changed, 57 insertions(+), 3 deletions(-)
> create mode 100644 net/bluetooth/msft.c
> create mode 100644 net/bluetooth/msft.h
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 3bdec42c9612..0fe47708d3c8 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -21,6 +21,7 @@
> #include <net/bluetooth/bluetooth.h>
> #include <net/bluetooth/hci_core.h>
>
> +#include "../../net/bluetooth/msft.h"

This was my bad. I didn’t realized that drivers need to the set the opcode and not the core. I updated the patches to fix this.

> #include "btintel.h"
> #include "btbcm.h"
> #include "btrtl.h"
> @@ -58,6 +59,7 @@ static struct usb_driver btusb_driver;
> #define BTUSB_CW6622 0x100000
> #define BTUSB_MEDIATEK 0x200000
> #define BTUSB_WIDEBAND_SPEECH 0x400000
> +#define BTUSB_MSFT_VND_EXT 0x800000
>
> static const struct usb_device_id btusb_table[] = {
> /* Generic Bluetooth USB device */
> @@ -335,7 +337,8 @@ static const struct usb_device_id blacklist_table[] = {
>
> /* Intel Bluetooth devices */
> { USB_DEVICE(0x8087, 0x0025), .driver_info = BTUSB_INTEL_NEW |
> - BTUSB_WIDEBAND_SPEECH },
> + BTUSB_WIDEBAND_SPEECH |
> + BTUSB_MSFT_VND_EXT },
> { USB_DEVICE(0x8087, 0x0026), .driver_info = BTUSB_INTEL_NEW |
> BTUSB_WIDEBAND_SPEECH },
> { USB_DEVICE(0x8087, 0x0029), .driver_info = BTUSB_INTEL_NEW |
> @@ -348,7 +351,8 @@ static const struct usb_device_id blacklist_table[] = {
> { USB_DEVICE(0x8087, 0x0aa7), .driver_info = BTUSB_INTEL |
> BTUSB_WIDEBAND_SPEECH },
> { USB_DEVICE(0x8087, 0x0aaa), .driver_info = BTUSB_INTEL_NEW |
> - BTUSB_WIDEBAND_SPEECH },
> + BTUSB_WIDEBAND_SPEECH |
> + BTUSB_MSFT_VND_EXT },

Lets start with ThunderPeak 0x0025 for now. We are looking into enabling this in a more generic fashion, but for now lets just enable one card.

>
> /* Other Intel Bluetooth devices */
> { USB_VENDOR_AND_INTERFACE_INFO(0x8087, 0xe0, 0x01, 0x01),
> @@ -3800,6 +3804,9 @@ static int btusb_probe(struct usb_interface *intf,
> set_bit(HCI_QUIRK_STRICT_DUPLICATE_FILTER, &hdev->quirks);
> set_bit(HCI_QUIRK_SIMULTANEOUS_DISCOVERY, &hdev->quirks);
> set_bit(HCI_QUIRK_NON_PERSISTENT_DIAG, &hdev->quirks);
> +
> + if (id->driver_info & BTUSB_MSFT_VND_EXT)
> + msft_set_opcode(hdev, 0xFC1E);
> }
>
> if (id->driver_info & BTUSB_MARVELL)
> diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h
> index d4e28773d378..239cae2d9998 100644
> --- a/include/net/bluetooth/hci_core.h
> +++ b/include/net/bluetooth/hci_core.h
> @@ -484,6 +484,10 @@ struct hci_dev {
> struct led_trigger *power_led;
> #endif
>
> +#if IS_ENABLED(CONFIG_BT_MSFTEXT)
> + __u16 msft_opcode;
> +#endif
> +
> int (*open)(struct hci_dev *hdev);
> int (*close)(struct hci_dev *hdev);
> int (*flush)(struct hci_dev *hdev);
> diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig
> index 165148c7c4ce..5929ccb02b39 100644
> --- a/net/bluetooth/Kconfig
> +++ b/net/bluetooth/Kconfig
> @@ -30,7 +30,7 @@ menuconfig BT
> L2CAP (Logical Link Control and Adaptation Protocol)
> SMP (Security Manager Protocol) on LE (Low Energy) links
> HCI Device drivers (Interface to the hardware)
> - RFCOMM Module (RFCOMM Protocol)
> + RFCOMM Module (RFCOMM Protocol)

Unrelated changes don’t belong here.

> BNEP Module (Bluetooth Network Encapsulation Protocol)
> CMTP Module (CAPI Message Transport Protocol)
> HIDP Module (Human Interface Device Protocol)
> @@ -93,6 +93,13 @@ config BT_LEDS
> This option selects a few LED triggers for different
> Bluetooth events.
>
> +config BT_MSFTEXT
> + bool "Enable Microsoft extensions"
> + depends on BT
> + help
> + This options enables support for the Microsoft defined HCI
> + vendor extensions.
> +
> config BT_SELFTEST
> bool "Bluetooth self testing support"
> depends on BT && DEBUG_KERNEL
> diff --git a/net/bluetooth/Makefile b/net/bluetooth/Makefile
> index fda41c0b4781..41dd541a44a5 100644
> --- a/net/bluetooth/Makefile
> +++ b/net/bluetooth/Makefile
> @@ -19,5 +19,6 @@ bluetooth-y := af_bluetooth.o hci_core.o hci_conn.o hci_event.o mgmt.o \
> bluetooth-$(CONFIG_BT_BREDR) += sco.o
> bluetooth-$(CONFIG_BT_HS) += a2mp.o amp.o
> bluetooth-$(CONFIG_BT_LEDS) += leds.o
> +bluetooth-$(CONFIG_BT_MSFTEXT) += msft.o
> bluetooth-$(CONFIG_BT_DEBUGFS) += hci_debugfs.o
> bluetooth-$(CONFIG_BT_SELFTEST) += selftest.o
> diff --git a/net/bluetooth/msft.c b/net/bluetooth/msft.c
> new file mode 100644
> index 000000000000..7609932c48ca
> --- /dev/null
> +++ b/net/bluetooth/msft.c
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/* Copyright (C) 2020 Google Corporation */
> +
> +#include <net/bluetooth/bluetooth.h>
> +#include <net/bluetooth/hci_core.h>
> +
> +#include "msft.h"
> +
> +void msft_set_opcode(struct hci_dev *hdev, __u16 opcode)
> +{
> + hdev->msft_opcode = opcode;
> +
> + bt_dev_info(hdev, "Enabling MSFT extensions with opcode 0x%2.2x",
> + hdev->msft_opcode);
> +}
> +EXPORT_SYMBOL(msft_set_opcode);
> diff --git a/net/bluetooth/msft.h b/net/bluetooth/msft.h
> new file mode 100644
> index 000000000000..7218ea759dde
> --- /dev/null
> +++ b/net/bluetooth/msft.h
> @@ -0,0 +1,19 @@
> +/* SPDX-License-Identifier: GPL-2.0-or-later */
> +/* Copyright (C) 2020 Google Corporation */
> +
> +#ifndef __MSFT_H
> +#define __MSFT_H
> +
> +#include <net/bluetooth/hci_core.h>
> +
> +#if IS_ENABLED(CONFIG_BT_MSFTEXT)
> +
> +void msft_set_opcode(struct hci_dev *hdev, __u16 opcode);
> +
> +#else
> +
> +static inline void msft_set_opcode(struct hci_dev *hdev, __u16 opcode) {}
> +
> +#endif
> +
> +#endif /* __MSFT_H*/

Regards

Marcel

\
 
 \ /
  Last update: 2020-03-31 00:07    [W:0.077 / U:7.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site