On 10/08/15 21:11, Benjamin Tissoires wrote: > I am currently running v4.2-rc6, merged with Dmitry's and Jiri's tree. > This patch completely kills my touchpad on the Pixel 2. No touch > information is sent while the physical button still emits values. You > said that you tested it on this laptop too, so I wonder why mine > refuses to work. I'm just building that version to see if I can reproduce. Dmitry made some minor changes when he merged it, but I don't think it should have affected anything. Are you able to send me some dmesg output with dyndbg=+pt enabled? It would also be useful if you could compile mxt-app and try issuing a calibrate or reset command to see if that restores touch (let me know if you need instructions). > It looks also that the deep sleep gets kept while rebooting a > different kernel. If I reboot to the standard fedora kernel (without > this patch), I still have the same problem, and I have to reboot under > ChromeOS to get the touchpad back alive. Then, the Fedora kernel works > just fine. That's unfortunate. In an ideal world the Fedora kernel driver should reset the touch controller or at least check the power settings, and it appears it's doing neither. -- 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
