Hi AceLan,
> We found an issue that when system enters S3, it stays in S3 for a few
> seconds, and somehow it resumes automatically.
> And we try below quirk which can prevent it from waking up.
>
> drivers/usb/core/quirks.c
> @@ -208,11 +208,11 @@ static const struct usb_device_id usb_quirk_list[] = {
> USB_QUIRK_DISCONNECT_SUSPEND },
> { USB_DEVICE(0x12d1, 0x15c3), .driver_info =
> USB_QUIRK_DISCONNECT_SUSPEND },
> + { USB_DEVICE(0x8087, 0x0025), .driver_info =
> + USB_QUIRK_DISCONNECT_SUSPEND },
>
> Here are some findings from the system.
>
> $ lsusb
> Bus 001 Device 004: ID 8087:0025 Intel Corp.
can we be a bit more specific here on what is going on and triage this a bit more. I have not heard of our hardware needing such a broad quirk. Also disconnecting on suspend means that we loose the support for remote wakeup and I am pretty sure that we do not want that.
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
