diff options
| author | Daniel Drake <drake@endlessm.com> | 2015-05-21 16:23:50 +0200 |
|---|---|---|
| committer | Marcel Holtmann <marcel@holtmann.org> | 2015-05-25 21:03:06 +0200 |
| commit | 04b8c8143d46453a443ac32bfcd76ec952605765 (patch) | |
| tree | e5a5c87fc3cd6acc217a0ceadcd64bb813ffb66d /drivers/mfd/da9052-i2c.c | |
| parent | Bluetooth: hci_uart: Change 1 to true for bool type variables assignments (diff) | |
| download | linux-04b8c8143d46453a443ac32bfcd76ec952605765.tar.xz linux-04b8c8143d46453a443ac32bfcd76ec952605765.zip | |
Bluetooth: btusb: fix Realtek suspend/resume
Realtek btusb devices don't currently work after suspend/resume because
the updated firmware is quietly lost - the USB hub doesn't notice any
status change upon resume, but some kind of reset has definitely
happened as the LMP subversion has reverted to its original value.
Set the reset_resume flag to trigger probe and upload the new firmware
again.
Like the vendor code, I assume this is not needed when the device is
selected as a wakeup source and hence will retain power during suspend.
On the 2 products I have to hand, when trying this configuration the
hardware seems unable to keep the device powered up during suspend.
The USB hub then detects a status change on resume and does a reset,
so we do not end up in broken state.
Signed-off-by: Daniel Drake <drake@endlessm.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/mfd/da9052-i2c.c')
0 files changed, 0 insertions, 0 deletions