On Tue, Aug 27, 2013 at 01:23:52PM +0200, David Herrmann wrote:
> 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.
> 
> Signed-off-by: David Herrmann <[email protected]>
> ---
>  include/uapi/linux/input.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/include/uapi/linux/input.h b/include/uapi/linux/input.h
> index 4649ee3..2fb6fae 100644
> --- a/include/uapi/linux/input.h
> +++ b/include/uapi/linux/input.h
> @@ -194,6 +194,8 @@ struct input_keymap_entry {
>  #define SYN_CONFIG           1
>  #define SYN_MT_REPORT                2
>  #define SYN_DROPPED          3
> +#define SYN_MAX                      0xf
> +#define SYN_CNT                      (SYN_MAX+1)
>  
>  /*
>   * Keys and buttons
> -- 
> 1.8.4

yes please!

Acked-by: Peter Hutterer <[email protected]>

Cheers,
   Peter

--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to