Messages in this thread |  | | Subject | Re: [PATCH] Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" version | From | Kai-Heng Feng <> | Date | Sun, 18 Feb 2018 16:13:13 +0800 |
| |
> On 16 Feb 2018, at 8:10 PM, Hans de Goede <hdegoede@redhat.com> wrote: > > > Ok, I've asked the reporter of: > > https://bugzilla.redhat.com/show_bug.cgi?id=1514836 > > Which is how I got involved in this to provide DMI data and > I will whip up a patch for his machine and ask him to test > and once that is done submit upstream. This is the only machine > I'm aware of though and looking at the history of this I think > there will be others.
I have one machine needs the quirk. I’ll also send a patch to match its DMI.
Kai-Heng
> >> I addition we can add a module option to btusb.ko that allows us to force this flag to be set. That way testing this is easy on a vendor kernel. A bunch of the btusb quirks (and also core quirks) can be tested via module options or debugfs. > > Yes a module option for this is a good idea. > > Regards, > > Hans > >
|  |