Bluetooth: btusb: Whitespace fixes for btusb_setup_csr()

Bugzilla: http://bugzilla.redhat.com/2124521

commit aa17e8ce1c20619af46fc2b472aa2d1c5e50c3cc
Author: Ismael Ferreras Morezuelas <swyterzone@gmail.com>
Date:   Tue Jan 18 09:04:19 2022 +0100

    Bluetooth: btusb: Whitespace fixes for btusb_setup_csr()

    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>

Signed-off-by: Gopal Tiwari <gtiwari@redhat.com>
This commit is contained in:
Gopal Tiwari 2022-10-18 10:30:05 +05:30
parent 900b808ef6
commit 177305e19c
1 changed files with 3 additions and 3 deletions

View File

@ -2065,10 +2065,10 @@ static int btusb_setup_csr(struct hci_dev *hdev)
* These controllers are really messed-up.
*
* 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
* on their bulk RX endpoint from e.g. a keyboard or mouse
* (IOW remote-wakeup support is broken for the bulk endpoint).
* on their bulk RX endpoint from e.g. a keyboard or mouse
* (IOW remote-wakeup support is broken for the bulk endpoint).
*
* To fix 1. enable runtime-suspend, force-suspend the
* HCI and then wake-it up by disabling runtime-suspend.