diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2018-04-27 12:26:43 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-05-16 11:10:30 +0300 |
| commit | 4aa9ef8a29ad2f26ebff93ca9a410d59b243a63d (patch) | |
| tree | 4099721591034c4b054f562e77f42ef9b7d17345 /drivers/thermal | |
| parent | 4fcd0333b21e44e48c110a454b0baf696cbfc326 (diff) | |
| download | linux-4aa9ef8a29ad2f26ebff93ca9a410d59b243a63d.tar.xz | |
Bluetooth: btusb: Only check needs_reset_resume DMI table for QCA rome chipsets
commit fc54910280eb38bde923cdf0898e74687d8e6989 upstream.
Jeremy Cline correctly points out in rhbz#1514836 that a device where the
QCA rome chipset needs the USB_QUIRK_RESET_RESUME quirk, may also ship
with a different wifi/bt chipset in some configurations.
If that is the case then we are needlessly penalizing those other chipsets
with a reset-resume quirk, typically causing 0.4W extra power use because
this disables runtime-pm.
This commit moves the DMI table check to a btusb_check_needs_reset_resume()
helper (so that we can easily also call it for other chipsets) and calls
this new helper only for QCA_ROME chipsets for now.
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1514836
Cc: stable@vger.kernel.org
Cc: Jeremy Cline <jcline@redhat.com>
Suggested-by: Jeremy Cline <jcline@redhat.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/thermal')
0 files changed, 0 insertions, 0 deletions