Some devices provides the actual timestamp (hid_dg_scan_time in win8 ones) computed by the hardware itself. This value is global to the frame and is not specific to the multitouch protocol.
Unified · Split
| @@ -196,6 +196,17 @@ EV_MSC: · 195 unmodified lines | ||
| 196 | 196 | EV_MSC events are used for input and output events that do not fall under other |
| 197 | 197 | categories. |
| 198 | 198 | |
| 199 | +A few EV_MSC codes have special meaning: | |
| 200 | + | |
| 201 | +* MSC_TIMESTAMP: | |
| 202 | + - Used to report the number of microseconds since the last reset. This event | |
| 203 | + should be coded as an uint32 value, which is allowed to wrap around with | |
| 204 | + no special consequence. It is assumed that the time difference between two | |
| 205 | + consecutive events is reliable on a reasonable time scale (hours). | |
| 206 | + A reset to zero can happen, in which case the time since the last event is | |
| 207 | + unknown. If the device does not provide this information, the driver must | |
| 208 | + not provide it to user space. | |
| 209 | + | |
| 199 | 210 | EV_LED: |
| 200 | 211 | ---------- |
| 201 | 212 | EV_LED events are used for input and output to set and query the state of |
| @@ -851,6 +851,7 @@ struct input_keymap_entry { · 850 unmodified lines | ||
| 851 | 851 | #define MSC_GESTURE 0x02 |
| 852 | 852 | #define MSC_RAW 0x03 |
| 853 | 853 | #define MSC_SCAN 0x04 |
| 854 | +#define MSC_TIMESTAMP 0x05 | |
| 854 | 855 | #define MSC_MAX 0x07 |
| 855 | 856 | #define MSC_CNT (MSC_MAX+1) |
| 856 | 857 | |