On Tue, Oct 13, 2015 at 07:59:17PM +0000, Zooko Wilcox-O'Hearn wrote:

This is the complete output of running evtest and choosing option 10,
from the console (while X is running, but I'm not running evtest under
X).

zooko@spark ~ $ sudo evtest
No device specified, trying to scan all of /dev/input/event*

...

  Property type 0 (INPUT_PROP_POINTER)
  Property type 2 (INPUT_PROP_BUTTONPAD)
Testing ... (interrupt to exit)

I see. I wonder if configuration data stored in controller's NVRAM was
reset somehow. You can try extracting that data from Chrome OS
repository [1] (I believe this is a public link).

Rename files from *.raw into link-*.raw and drop them in /lib/firmware
Then apply the 2 attached patches and see if it will bring the touch
back to life.

Thanks!

-- 
Dmitry

[1]
https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/master/overlay-link/chromeos-base/chromeos-touch-config-link/files/