From: Oliver Neukum <oneukum@suse.com>
To: jflf_kernel@gmx.com, Oliver Neukum <oneukum@suse.com>,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: add quirks for Lenovo OneLink+ Dock
Date: Tue, 30 Aug 2022 16:47:29 +0200 [thread overview]
Message-ID: <4b92eee0-b020-9211-2039-18ac3ac72a7b@suse.com> (raw)
In-Reply-To: <d1a5f149-50a1-49fc-9a6d-eceffa23311b@gmx.com>
On 30.08.22 15:56, jflf_kernel@gmx.com wrote:
Hi,
> I agree that USB_QUIRK_RESET_RESUME seems fishy with a hub. It's pretty much the last quirk I tried, and the only one that worked. I can't say I understand what it does exactly.
Two things
1) force a reset after a resume and call reset_resume() instead of resume()
2) block autosuspend if remote wakeup is required
I suspect you are actually using the second effect. Have you
tested with "usbcore.autosuspend=-1" on the kernel command line.
The hubs themselves don't seem to reset (or at least not fully), as
there is no re-enumeration of existing children.
Probably because they do not suspend at all. Generally hubs do need
remote wakeup lest they forget the port whose activity woke the system.
> I have not experienced a single problem or side effect since using those quirks. I use a mix of USB 2.0 and 3.0 devices, some bus- and some self-powered, some permanently connected (including ethernet and audio in the hub itself) and some not.
The interesting test would be to see whether a keyboard, ethernet
or mouse can wake your system from suspend. Have you tested WOL?
Regards
Oliver
next prev parent reply other threads:[~2022-08-30 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 16:09 [PATCH] usb: add quirks for Lenovo OneLink+ Dock JFLF
2022-08-24 16:19 ` Greg KH
2022-08-30 11:54 ` Oliver Neukum
2022-08-30 13:56 ` jflf_kernel
2022-08-30 14:47 ` Oliver Neukum [this message]
2022-08-30 19:50 ` jflf_kernel
2022-08-31 7:31 ` Greg KH
2022-08-31 7:43 ` jflf_kernel
2022-08-31 8:35 ` Greg KH
2022-08-31 9:16 ` Oliver Neukum
2022-09-04 21:38 ` jflf_kernel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b92eee0-b020-9211-2039-18ac3ac72a7b@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=jflf_kernel@gmx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox