Same problem for me - on 16.04.

Apparently (I haven't tested), your fix works with kernel 4.6.  See bbs.archlinux.org/viewtopic.php

After some experiments, this did work for me:

$ sudo inputattach --daemon -w8001 /dev/ttyS4

...what I don't understand, because my ELAN Touchscreen is definitely not on serial port so there should not be reason to use inputattach at all.

The problem with this is that inputattach process gets D status (uninterruptible sleep) so it makes the suspend/resume to take about 20 seconds (which is some timeout) and sometimes it does not work at all. Since you cannot kill this proccess, it is quite sad and it might imply any other issues eventually.

So this is not solution but might be some indice to find out what the real problem is. I also see this:

$ dmesg | grep -ie elan
[ 7.637031] usb 1-4: Manufacturer: ELAN
[ 10.101754] input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:20D0.0001/input/input12
[ 10.101852] hid-multitouch 0003:04F3:20D0.0001: input,hiddev0,hidraw0: USB HID v1.10 Device [ELAN Touchscreen] on usb-0000:00:14.0-4/input0
[ 698.403796] input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:20D0.0001/input/input18
[ 698.404299] hid-multitouch 0003:04F3:20D0.0001: input,hiddev0,hidraw0: USB HID v1.10 Device [ELAN Touchscreen] on usb-0000:00:14.0-4/input0

...I wonder why it is input18 instead of input12 after first resume (might change after another suspend/resume?!). So maybe, there is something waiting for input12 but it has changed to input18 while something expects it on 12? I don't know.

That's just my two cents, and I am hefeby joining the question how to fix this completely and properly :)

Yes, I confirm that works for me too.  With the 4.4 kernel, 16.04.

Awesome find :-)  Works well.

Wonderful! I did it very quickly so that I didn't have to press the power button and it just locked screen and started to work again. Given this, we may be able to do some kernel debugging now...

Yeah, the quick lid close works for me as well. Weird.

Any luck debugging this further?

Can also confirm same workaround works. Don't even have to close the lid fully, just move it down a bit then up - the display doesn't even go dark - and touch is working again.

This seems to still be an issue with the latest 1.4.4 firmware. It's not that big of a deal to me given the workaround of closing it and then opening it again right away seems to fix it.

Did you solve the problem?