Hi Nick, On Mon, Aug 3, 2015 at 11:23 AM, Nick Dyer <nick.dyer@xxxxxxxxxxx> wrote: > The hardcoded 0x83 CTRL setting overrides other settings in that byte, > enabling extra reporting that may not be useful on a particular platform. > > Implement improved suspend mechanism via deep sleep. By writing zero to > both the active and idle cycle times the maXTouch device can be put into a > deep sleep mode, using minimal power. It is necessary to issue a calibrate > command after the chip has spent any time in deep sleep, however a soft > reset is unnecessary. > > Use the old method on Chromebook Pixel via platform data option. > > This patch also deals with the situation where the power configuration is > zero on probe, which would mean that the device never wakes up to execute > commands. > > After a config download, the T7 power configuration may have changed so it > is necessary to re-read it. > > Signed-off-by: Nick Dyer <nick.dyer@xxxxxxxxxxx> > Acked-by: Benson Leung <bleung@xxxxxxxxxxxx> > Acked-by: Yufeng Shen <miletus@xxxxxxxxxxxx> > --- 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. 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. Any ideas why? Cheers, Benjamin -- 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
