On Sun, 17 Nov 2019, Ikjoon Jang wrote: > This patchset enables hard wired hub device to use different bInterval > from its descriptor when the hub has a combined device node. > > When we know the specific hard wired hub supports changing its polling > interval, we can adjust hub's interval to reduce the time of waking up > from autosuspend or connect detection of HIDs. In fact, _all_ hubs support changing the polling interval. The value given in the USB spec is just an upper limit; any smaller value is equally acceptable. So why are you doing this only for hard-wired hubs? Why not for all hubs? And is 250 ms really too long to wait for remote wakeup or connect detection? What's the real motivation behind this change? Alan Stern
