Hi, On 3/24/24 10:07 PM, Mark Pearson wrote: > Add support for new input events on Lenovo laptops that need exporting to > user space. > > Lenovo trackpoints are adding the ability to generate a doubletap event. > Add a new keycode to allow this to be used by userspace. > > Lenovo support is using FN+N with Windows to collect needed details for > support cases. Add a keycode so that we'll be able to provide similar > support on Linux. > > Suggested-by: Peter Hutterer <peter.hutterer@xxxxxxxxxx> > > Signed-off-by: Mark Pearson <mpearson-lenovo@xxxxxxxxx> > Signed-off-by: Nitin Joshi <njoshi1@xxxxxxxxxx> > Signed-off-by: Vishnu Sankar <vsankar@xxxxxxxxxx> Thanks, patch looks good to me: Reviewed-by: Hans de Goede <hdegoede@xxxxxxxxxx> Dmitry, can I have your ack for merging this change through the pdx86 tree (since the first driver using these is a pdx86 driver) ? Regards, Hans > --- > include/uapi/linux/input-event-codes.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h > index 03edf2ccdf6c..bd3baca95749 100644 > --- a/include/uapi/linux/input-event-codes.h > +++ b/include/uapi/linux/input-event-codes.h > @@ -686,6 +686,8 @@ > #define KEY_SIDEVU_SONAR 0x287 > #define KEY_NAV_INFO 0x288 > #define KEY_BRIGHTNESS_MENU 0x289 > +#define KEY_DOUBLECLICK 0x28a > +#define KEY_SYS_DEBUG_INFO 0x28b > > /* > * Some keyboards have keys which do not have a defined meaning, these keys
