evdevtouch: Disable threading.

This should never have been threaded. It isn't resource-intensive, and it needs
to communicate touches back to the main thread anyway.

Removing the threading significantly(!) improves latency.
evdevtouch: Don't try to keep reading if we get EAGAIN.

This stops touching the screen (and not moving) consuming 80-90% CPU. :)
Merge branch 'master' of github.com:mer-packages/qtbase
Fix dead lock in the Qt event handling

The deadlock is caused because the QEvent is destroyed while holding the
event list mutex. And the QEvent may have a custom destructor that will
re-enter the event handlng code.

The QScopedPointer that should destroy the event must be created after
the MutexUnlocker.

Regression introduced by commit f9035587b98ac5dc9491e642b8ec84470ec03f0e

Task-number: QTBUG-31606
Change-Id: I6b2cbc2656eacdec61b641886953f00bf5b3ff36
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Merge branch 'master' of github.com:mer-packages/qtbase
[patch] Increment loopLevel prior to emitting aboutToBlock()/awake() signals

Without this, any deferred delete actions that occur as a result of
these signals will not be processed until the main event loop exits.

This is triggered by the QtWayland server, which uses aboutToBlock() to
process internal events such as surface destruction.
Merge pull request #9 from aaronkennedy/master

[patch] Increment loopLevel prior to emitting aboutToBlock()/awake() sig...