summaryrefslogtreecommitdiff
path: root/Documentation/DMA-API.txt
diff options
context:
space:
mode:
authorHans de Goede <hdegoede@redhat.com>2018-04-27 11:26:43 +0200
committerMarcel Holtmann <marcel@holtmann.org>2018-04-30 10:50:45 +0200
commitfc54910280eb38bde923cdf0898e74687d8e6989 (patch)
treea161edc028f3ee47df4430bd316aeea23af2c1eb /Documentation/DMA-API.txt
parent544a591668813583021474fa5c7ff4942244d654 (diff)
downloadlwn-fc54910280eb38bde923cdf0898e74687d8e6989.tar.gz
lwn-fc54910280eb38bde923cdf0898e74687d8e6989.zip
Bluetooth: btusb: Only check needs_reset_resume DMI table for QCA rome chipsets
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>
Diffstat (limited to 'Documentation/DMA-API.txt')
0 files changed, 0 insertions, 0 deletions