On Fri, 2010-04-23 at 09:53 -0700, Dmitry Torokhov wrote: > On Thursday 22 April 2010 05:47:48 pm Christoph Fritz wrote: > > in conclusion: > > If a Synaptics touchpad can't be initialized (synaptics_init) and falls > > back to PS/2, it doesn't get a psmouse_reset() after resuming from > > suspend as it would get with a synaptics driver. > > Yes, you are right. Maybe we should just reset psmouse unconditionally in > psmouse_reconnect() before actually doing any protocol reconnect/reprobe. That > should help in cases when users not enable Synaptics support; also it is > probably unlikely that mouse that was there gets unplugged after resume. Yes, this would solve that case too. Maybe if we take that "unconditionally-reset-step", what about taking the full step and getting rid of the whole i8042_dmi_reset_table quirk stuff and doing unconditionally resets there too? -- 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
