iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bluetooth: btusb: Whitespace fixes for btusb_setup_csr()

Browse Source 
Properly align the list items of the quirk for readability.
No functional changes intended. Trivial stuff.

Fixes: 0671c06623 ("Bluetooth: btusb: Add workaround for remote-wakeup issues with Barrot 8041a02 fake CSR controllers")
Signed-off-by: Ismael Ferreras Morezuelas <swyterzone@gmail.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:
Ismael Ferreras Morezuelas
2022-01-18 09:04:19 +01:00
committed by Marcel Holtmann
parent 2e7b4a328e
commit aa17e8ce1c
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
drivers/bluetooth/btusb.c
View File

@@ -2062,10 +2062,10 @@ static int btusb_setup_csr(struct hci_dev *hdev)
* These controllers are really messed-up. * These controllers are really messed-up.
* *
* 1. Their bulk RX endpoint will never report any data unless * 1. Their bulk RX endpoint will never report any data unless
* the device was suspended at least once (yes, really). * the device was suspended at least once (yes, really).
* 2. They will not wakeup when autosuspended and receiving data * 2. They will not wakeup when autosuspended and receiving data
* on their bulk RX endpoint from e.g. a keyboard or mouse * on their bulk RX endpoint from e.g. a keyboard or mouse
* (IOW remote-wakeup support is broken for the bulk endpoint). * (IOW remote-wakeup support is broken for the bulk endpoint).
* *
* To fix 1. enable runtime-suspend, force-suspend the * To fix 1. enable runtime-suspend, force-suspend the
* HCI and then wake-it up by disabling runtime-suspend. * HCI and then wake-it up by disabling runtime-suspend.