[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACK8Z6FNmZFW9c=1tY4Q4rn4ZyUu--CUTuLk0SHZsuYb1-H7Og@mail.gmail.com>
Date: Thu, 12 Mar 2020 12:32:46 -0700
From: Rajat Jain <rajatja@...gle.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-input@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dmitry Torokhov <dtor@...gle.com>
Subject: Re: [PATCH v2] Input: Allocate keycode for SNIP key
Hi Dmitry,
On Tue, Mar 3, 2020 at 4:21 PM Rajat Jain <rajatja@...gle.com> wrote:
>
> New chromeos keyboards have a "snip" key that is basically a selective
> screenshot (allows a user to select an area of screen to be copied).
> Allocate a keyvode for it.
Any comments on this patch?
Thanks & Best Regards,
Rajat
>
> Signed-off-by: Rajat Jain <rajatja@...gle.com>
> ---
> V2: Drop patch [1/2] and instead rebase this on top of Linus' tree.
>
> include/uapi/linux/input-event-codes.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h
> index 0f1db1cccc3fd..08c8572891efb 100644
> --- a/include/uapi/linux/input-event-codes.h
> +++ b/include/uapi/linux/input-event-codes.h
> @@ -652,6 +652,9 @@
> /* Electronic privacy screen control */
> #define KEY_PRIVACY_SCREEN_TOGGLE 0x279
>
> +/* Selective Screenshot */
> +#define KEY_SNIP 0x280
> +
> /*
> * Some keyboards have keys which do not have a defined meaning, these keys
> * are intended to be programmed / bound to macros by the user. For most
> --
> 2.25.0.265.gbab2e86ba0-goog
>
Powered by blists - more mailing lists