[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+jURctTtUCJyD0Rdd+urMiaASqyipg_mPrOBW3CEdmkVWHeOA@mail.gmail.com>
Date: Fri, 13 Mar 2020 11:05:24 -0700
From: Harry Cutts <hcutts@...omium.org>
To: Rajat Jain <rajatja@...gle.com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-input <linux-input@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
Dmitry Torokhov <dtor@...gle.com>, rajatxjain@...il.com
Subject: Re: [PATCH v3] Input: Allocate keycode for "Selective Screenshot" key
On Fri, 13 Mar 2020 at 11:03, 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 keycode for it.
>
> Signed-off-by: Rajat Jain <rajatja@...gle.com>
Reviewed-by: Harry Cutts <hcutts@...omium.org>
Harry Cutts
Chrome OS Touch/Input team
> ---
> v3: Rename KEY_SNIP to KEY_SELECTIVE_SNAPSHOT
> V2: Drop patch [1/2] and instead rebase this on top of Linus' tree.
>
> 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 0f1db1cccc3fd..c4dbe2ee9c098 100644
> --- a/include/uapi/linux/input-event-codes.h
> +++ b/include/uapi/linux/input-event-codes.h
> @@ -652,6 +652,8 @@
> /* Electronic privacy screen control */
> #define KEY_PRIVACY_SCREEN_TOGGLE 0x279
>
> +#define KEY_SELECTIVE_SCREENSHOT 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.1.481.gfbce0eb801-goog
>
Powered by blists - more mailing lists