SYN_* events are special and not enabled via set_bit() for devices. Hence, they haven't been really needed, yet. However, user-space can still make great use of that for int->string debugging helpers or alike. Also, I haven't seen any reason not to define these, so here they are.
Showing the changes to include/uapi/linux (1 of 1 file). Show all
Unified · Split
| @@ -194,6 +194,8 @@ struct input_keymap_entry { · 193 unmodified lines | |||
| 194 | #define SYN_CONFIG 1 | 194 | #define SYN_CONFIG 1 |
| 195 | #define SYN_MT_REPORT 2 | 195 | #define SYN_MT_REPORT 2 |
| 196 | #define SYN_DROPPED 3 | 196 | #define SYN_DROPPED 3 |
| 197 | #define SYN_MAX 0xf | ||
| 198 | #define SYN_CNT (SYN_MAX+1) | ||
| 197 | 199 | ||
| 198 | /* | 200 | /* |
| 199 | * Keys and buttons | 201 | * Keys and buttons |