Bluetooth: btusb: Remove Yoga 920 from the btusb_needs_reset_resume_table
authorHans de Goede <hdegoede@redhat.com>
Wed, 28 Feb 2018 10:57:50 +0000 (11:57 +0100)
committerMarcel Holtmann <marcel@holtmann.org>
Thu, 1 Mar 2018 18:55:56 +0000 (19:55 +0100)
commitf0e8c61110c2c85903b136ba070daf643a8b6842
treeead98a68fd12ac1fa68bdd80b97833d503a33da0
parent773daa3caf5d3f87fdb1ab43e9c1b367a38fa394
Bluetooth: btusb: Remove Yoga 920 from the btusb_needs_reset_resume_table

Commit 1fdb92697469 ("Bluetooth: btusb: Use DMI matching for QCA
reset_resume quirking"), added the Lenovo Yoga 920 to the
btusb_needs_reset_resume_table.

Testing has shown that this is a false positive and the problems where
caused by issues with the initial fix: commit fd865802c66b ("Bluetooth:
btusb: fix QCA Rome suspend/resume"), which has already been reverted.

So the QCA Rome BT in the Yoga 920 does not need a reset-resume quirk at
all and this commit removes it from the btusb_needs_reset_resume_table.

Note that after this commit the btusb_needs_reset_resume_table is now
empty. It is kept around on purpose, since this whole series of commits
started for a reason and there are actually broken platforms around,
which need to be added to it.

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1514836
Fixes: 1fdb92697469 ("Bluetooth: btusb: Use DMI matching for QCA ...")
Cc: stable@vger.kernel.org
Cc: Brian Norris <briannorris@chromium.org>
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>
Tested-by: Kevin Fenzi <kevin@scrye.com>
Suggested-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Reviewed-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
drivers/bluetooth/btusb.c