HID core provides the same functionality and can convert the input event to a raw output report. We can thus drop UHID_OUTPUT_EV and rely on the mandatory UHID_OUTPUT. User-space wasn't able to do anything with UHID_OUTPUT_EV, anyway. They don't have access to the report fields.
Showing the changes to include/uapi/linux (1 of 3 files). Show all
Unified · Split
| @@ -30,7 +30,7 @@ enum uhid_event_type { · 29 unmodified lines | |||
| 30 | UHID_OPEN, | 30 | UHID_OPEN, |
| 31 | UHID_CLOSE, | 31 | UHID_CLOSE, |
| 32 | UHID_OUTPUT, | 32 | UHID_OUTPUT, |
| 33 | UHID_OUTPUT_EV, | 33 | UHID_OUTPUT_EV, /* obsolete! */ |
| 34 | UHID_INPUT, | 34 | UHID_INPUT, |
| 35 | UHID_FEATURE, | 35 | UHID_FEATURE, |
| 36 | UHID_FEATURE_ANSWER, | 36 | UHID_FEATURE_ANSWER, |
| @@ -69,6 +69,8 @@ struct uhid_output_req { · 32 unmodified lines | |||
| 69 | __u8 rtype; | 69 | __u8 rtype; |
| 70 | } __attribute__((__packed__)); | 70 | } __attribute__((__packed__)); |
| 71 | 71 | ||
| 72 | /* Obsolete! Newer kernels will no longer send these events but instead convert | ||
| 73 | * it into raw output reports via UHID_OUTPUT. */ | ||
| 72 | struct uhid_output_ev_req { | 74 | struct uhid_output_ev_req { |
| 73 | __u16 type; | 75 | __u16 type; |
| 74 | __u16 code; | 76 | __u16 code; |