On Fri, Oct 28, 2022 at 09:13:14PM -0400, Alan Stern wrote: > However, I'm curious to know why this patch makes ehci-pci use > PROBE_PREFER_ASYNCHRONOUS even when CONFIG_PM isn't set, whereas the 2/2 > patch makes xhci-pci use PROBE_PREFER_ASYNCHRONOUS only when CONFIG_PM > is set. That's definitely a bug in patch 2. This has nothing (or, little; probe order can technically affect the PM suspend/resume order) to do with CONFIG_PM, except that the .pm hooks tend to sit nearby, and repeated driver patching makes the author's eyes glaze over sometimes... Thanks. v2 coming. Brian
