On Wed, Nov 25, 2015 at 10:24:07AM -0500, Alan Stern wrote: > On Tue, 24 Nov 2015, Dmitry Torokhov wrote: > > > On Tue, Nov 24, 2015 at 4:58 PM, Todd Brandt > > <todd.e.brandt@xxxxxxxxxxxxxxx> wrote: > > > Delay the error rescan for serio devices until the PM > > > complete phase. PM complete requires locking each device > > > before checking for and executing the complete callbacks. > > > Serio rescan also locks the device in order to reinit on > > > error, so this can cause a conflict which will result in > > > unnecessary delay. > > > > > > History: > > > > > > The issue was discovered on an ivy bridge platform with > > > i8042 keyboard/mouse. The mouse resume fails > > > > I'd first try to figure out why reconnect failed. What kind of > > mouse/touchpad is that? > > > > > and the serio > > > driver begins a full driver rescan in the resume phase. Since > > > the device is locked during re-initialization it conflicts > > > with the PM subsystem's attempt to lock the device to check > > > for a complete callback. Thus dpm_complete is delayed for > > > almost a second. > > > > > > I've tried to fix this by altering the PM subsystem code > > > itself so that it doesn't have to lock a device in order to > > > check if it has a callback, but this was too much for an > > > isolated case. This approach attempts to fix the problem in > > > the serio driver itself. > > > > Hmm, there is nothing specific to serio here. Any slow-to-probe device > > might wedge the process like that. > > USB is a little similar. Probing can be slow, but it is carried out in > a workqueue thread. Since the workqueue is marked as FREEZABLE, it > doesn't run at all during any stage of system sleep, so the problem > can't arise. Serio used to have freezable workqueue, but because PS/2 protocol is slow we want to start talking to the device as soon as possible to minimize amount of time where UI is shown but user is "stuck" because mouse does not move. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
