QuoteHow did you meassure these values?
I toggle an output and showed this with the KO. By operating the display, the toggle signal is interrupted.
QuoteWhich kernel version are you using?
I work with Version 1.30.
I' ve just found out, that the priority of the touch driver is really 109. But it looks like this task call an other one with the priority 102.
Have you got any ideas which task this could by?
The system has only one thread with the priority of 109. When i change the priority of the touch driver, this thread changes his priority. But the can is interrupted as long as his priority is bigger than 102. When I'm operating the system with the mouse, the can isn't interrupted.