<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-linux/drivers/bluetooth, branch jd/unified-crypt-queue</title>
<subtitle>WireGuard for the Linux kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-linux/atom/drivers/bluetooth?h=jd%2Funified-crypt-queue</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-linux/atom/drivers/bluetooth?h=jd%2Funified-crypt-queue'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/'/>
<updated>2020-04-11T05:58:23Z</updated>
<entry>
<title>Bluetooth: btrtl: Add support for RTL8761B</title>
<updated>2020-04-11T05:58:23Z</updated>
<author>
<name>Ziqian SUN (Zamir)</name>
<email>sztsian@gmail.com</email>
</author>
<published>2020-04-11T01:34:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=04896832c94aae4842100cafb8d3a73e1bed3a45'/>
<id>urn:sha1:04896832c94aae4842100cafb8d3a73e1bed3a45</id>
<content type='text'>
Add new compatible device RTL8761B. RTL8761B is a USB Bluetooth device,
with support of BLE and BR/EDR. The USB info is

T:  Bus=03 Lev=04 Prnt=04 Port=00 Cnt=01 Dev#= 29 Spd=12   MxCh= 0
D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0bda ProdID=8771 Rev= 2.00
S:  Manufacturer=Realtek
S:  Product=Bluetooth Radio
S:  SerialNumber=XXXXXXXXXXXX
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms

Signed-off-by: Ziqian SUN (Zamir) &lt;sztsian@gmail.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btusb: check for NULL in btusb_find_altsetting()</title>
<updated>2020-04-08T06:16:56Z</updated>
<author>
<name>Sathish Narasimman</name>
<email>nsathish41@gmail.com</email>
</author>
<published>2020-04-08T05:27:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=fcd156ee8bc6a989dbf7e5efbccdc9cdb831fd27'/>
<id>urn:sha1:fcd156ee8bc6a989dbf7e5efbccdc9cdb831fd27</id>
<content type='text'>
The new btusb_find_altsetting() dereferences it without checking
the check is added in this patch

Signed-off-by: Sathish Narasimman &lt;sathish.narasimman@intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btusb: Enable MSFT extension for Intel ThunderPeak devices</title>
<updated>2020-04-05T11:53:09Z</updated>
<author>
<name>Miao-chen Chou</name>
<email>mcchou@chromium.org</email>
</author>
<published>2020-04-03T19:44:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=fc04590e3d39213a22b7afd46c4bd5d95a6cab1f'/>
<id>urn:sha1:fc04590e3d39213a22b7afd46c4bd5d95a6cab1f</id>
<content type='text'>
The Intel ThundePeak BT controllers support the Microsoft vendor
extension and they are using 0xFC1E for VsMsftOpCode.

&lt; HCI Command: Vendor (0x3f|0x001e) plen 1
        00
&gt; HCI Event: Command Complete (0x0e) plen 15
      Vendor (0x3f|0x001e) ncmd 1
        Status: Success (0x00)
        00 3f 00 00 00 00 00 00 00 01 50

Signed-off-by: Miao-chen Chou &lt;mcchou@chromium.org&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btusb: Enable Intel events even if already in operational mode</title>
<updated>2020-04-05T11:53:07Z</updated>
<author>
<name>Marcel Holtmann</name>
<email>marcel@holtmann.org</email>
</author>
<published>2020-04-03T19:44:02Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=7fd673bcdacc8528c7d9489d31f040eac7cca164'/>
<id>urn:sha1:7fd673bcdacc8528c7d9489d31f040eac7cca164</id>
<content type='text'>
In case the controller is already in operation mode, the Intel specific
events will not be enabled. Fix this by jumping to a common finish
section that will allow setting final details for the controller.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btusb: handle mSBC audio over USB Endpoints</title>
<updated>2020-04-05T11:52:59Z</updated>
<author>
<name>Sathish Narasimman</name>
<email>sathish.narasimman@intel.com</email>
</author>
<published>2020-04-03T19:43:59Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=baac6276c0a9f36f1fe1f00590ef00d2ba5ba626'/>
<id>urn:sha1:baac6276c0a9f36f1fe1f00590ef00d2ba5ba626</id>
<content type='text'>
For mSBC encoded audio stream over usb transport, btusb driver
to be set to alternate settings 6 as per BT core spec 5.0. The
type of air mode is used to differenting which alt setting to be
used.

The changes are made considering some discussion over the similar
patch submitted earlier from Kuba Pawlak (link below)
https://www.spinics.net/lists/linux-bluetooth/msg64577.html

Reported-by: kbuild test robot &lt;lkp@intel.com&gt;
Signed-off-by: Sathish Narasimman &lt;sathish.narasimman@intel.com&gt;
Signed-off-by: Chethan T N &lt;chethan.tumkur.narayan@intel.com&gt;
Signed-off-by: Hsin-Yu Chao &lt;hychao@chromium.org&gt;
Signed-off-by: Amit K Bag &lt;amit.k.bag@intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: fix freeing not-requested IRQ</title>
<updated>2020-04-03T06:39:19Z</updated>
<author>
<name>Michał Mirosław</name>
<email>mirq-linux@rere.qmqm.pl</email>
</author>
<published>2020-04-02T12:55:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=81bd5d0c62437c02caac6b3f942fcda874063cb0'/>
<id>urn:sha1:81bd5d0c62437c02caac6b3f942fcda874063cb0</id>
<content type='text'>
When BT module can't be initialized, but it has an IRQ, unloading
the driver WARNs when trying to free not-yet-requested IRQ. Fix it by
noting whether the IRQ was requested.

WARNING: CPU: 2 PID: 214 at kernel/irq/devres.c:144 devm_free_irq+0x49/0x4ca
[...]
WARNING: CPU: 2 PID: 214 at kernel/irq/manage.c:1746 __free_irq+0x8b/0x27c
Trying to free already-free IRQ 264
Modules linked in: hci_uart(-) btbcm bluetooth ecdh_generic ecc libaes
CPU: 2 PID: 214 Comm: rmmod Tainted: G        W         5.6.1mq-00044-ga5f9ea098318-dirty #928
[...]
[&lt;b016aefb&gt;] (devm_free_irq) from [&lt;af8ba1ff&gt;] (bcm_close+0x97/0x118 [hci_uart])
[&lt;af8ba1ff&gt;] (bcm_close [hci_uart]) from [&lt;af8b736f&gt;] (hci_uart_unregister_device+0x33/0x3c [hci_uart])
[&lt;af8b736f&gt;] (hci_uart_unregister_device [hci_uart]) from [&lt;b035930b&gt;] (serdev_drv_remove+0x13/0x20)
[&lt;b035930b&gt;] (serdev_drv_remove) from [&lt;b037093b&gt;] (device_release_driver_internal+0x97/0x118)
[&lt;b037093b&gt;] (device_release_driver_internal) from [&lt;b0370a0b&gt;] (driver_detach+0x2f/0x58)
[&lt;b0370a0b&gt;] (driver_detach) from [&lt;b036f855&gt;] (bus_remove_driver+0x41/0x94)
[&lt;b036f855&gt;] (bus_remove_driver) from [&lt;af8ba8db&gt;] (bcm_deinit+0x1b/0x740 [hci_uart])
[&lt;af8ba8db&gt;] (bcm_deinit [hci_uart]) from [&lt;af8ba86f&gt;] (hci_uart_exit+0x13/0x30 [hci_uart])
[&lt;af8ba86f&gt;] (hci_uart_exit [hci_uart]) from [&lt;b01900bd&gt;] (sys_delete_module+0x109/0x1d0)
[&lt;b01900bd&gt;] (sys_delete_module) from [&lt;b0101001&gt;] (ret_fast_syscall+0x1/0x5a)
[...]

Cc: stable@vger.kernel.org
Fixes: 6cc4396c8829 ("Bluetooth: hci_bcm: Add wake-up capability")
Signed-off-by: Michał Mirosław &lt;mirq-linux@rere.qmqm.pl&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: respect IRQ polarity from DT</title>
<updated>2020-04-03T06:39:19Z</updated>
<author>
<name>Michał Mirosław</name>
<email>mirq-linux@rere.qmqm.pl</email>
</author>
<published>2020-04-02T12:55:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=b25e4df4a83e516efbdeeefb5b2d3e259639a56e'/>
<id>urn:sha1:b25e4df4a83e516efbdeeefb5b2d3e259639a56e</id>
<content type='text'>
The IRQ polarity is be configured in bcm_setup_sleep(). Make the
configured value match what is in the DeviceTree.

Cc: stable@vger.kernel.org
Fixes: f25a96c8eb46 ("Bluetooth: hci_bcm: enable IRQ capability from devicetree")
Signed-off-by: Michał Mirosław &lt;mirq-linux@rere.qmqm.pl&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA6390</title>
<updated>2020-04-02T06:25:19Z</updated>
<author>
<name>Rocky Liao</name>
<email>rjliao@codeaurora.org</email>
</author>
<published>2020-03-25T02:26:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=e5d6468fe9d8dced9af0c548a359a7dbeb31c931'/>
<id>urn:sha1:e5d6468fe9d8dced9af0c548a359a7dbeb31c931</id>
<content type='text'>
This patch adds support for QCA6390, including the devicetree and acpi
compatible hwid matching, and patch/nvm downloading.

Signed-off-by: Rocky Liao &lt;rjliao@codeaurora.org&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btusb: print Intel fw build version in power-on boot</title>
<updated>2020-03-16T07:57:40Z</updated>
<author>
<name>Sukumar Ghorai</name>
<email>sukumar.ghorai@intel.com</email>
</author>
<published>2020-03-16T06:07:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=905d7b13112dcfdba1983c014f3bf30dc3d4f179'/>
<id>urn:sha1:905d7b13112dcfdba1983c014f3bf30dc3d4f179</id>
<content type='text'>
To determine the build version of Bluetooth firmware to ensure reported
issue related to a particular release. This is very helpful for every fw
downloaded to BT controller and issue reported from field test.

Signed-off-by: Amit K Bag &lt;amit.k.bag@intel.com&gt;
Signed-off-by: Sukumar Ghorai &lt;sukumar.ghorai@intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_h5: Switch from BT_ERR to bt_dev_err where possible</title>
<updated>2020-03-11T08:06:03Z</updated>
<author>
<name>Marcel Holtmann</name>
<email>marcel@holtmann.org</email>
</author>
<published>2020-03-09T21:57:23Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=bb0084ec893ebed123911e50c93f3b8ae8470531'/>
<id>urn:sha1:bb0084ec893ebed123911e50c93f3b8ae8470531</id>
<content type='text'>
All HCI device specific error messages shall use bt_dev_err to indicate
the device name in the message.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
</content>
</entry>
</feed>
