From: Bastien Nocera <hadess@hadess.net>
To: Rajat Jain <rajatja@google.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
dtor@google.com
Cc: rajatxjain@gmail.com
Subject: Re: [PATCH 1/2] Input: Add keycodes for keyboard backlight control
Date: Tue, 03 Mar 2020 09:15:02 +0100 [thread overview]
Message-ID: <fe4e0010826d4d18843b148dc088c2b01c7e2072.camel@hadess.net> (raw)
In-Reply-To: <20200303005645.237763-1-rajatja@google.com>
On Mon, 2020-03-02 at 16:56 -0800, Rajat Jain wrote:
> New keyboards can have backlight control keys. Allocating keycodes
> for them. Such keyboards are already available in ChromeOS.
>
> Signed-off-by: Rajat Jain <rajatja@google.com>
> ---
> include/uapi/linux/input-event-codes.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/include/uapi/linux/input-event-codes.h
> b/include/uapi/linux/input-event-codes.h
> index 0f1db1cccc3fd..e12a19dc30262 100644
> --- a/include/uapi/linux/input-event-codes.h
> +++ b/include/uapi/linux/input-event-codes.h
> @@ -652,6 +652,10 @@
> /* Electronic privacy screen control */
> #define KEY_PRIVACY_SCREEN_TOGGLE 0x279
>
> +/* Keyboard Backlight control */
> +#define KEY_KBD_BKLIGHT_UP 0x280
> +#define KEY_KBD_BKLIGHT_DOWN 0x281
There's already KEY_KBDILLUMDOWN and KEY_KBDILLUMUP, used since the
aluminium PowerBook G4 in 2005 (commit
146a4b3bdfb5641bfbf975e29680b482b8b343ba)
> +
> /*
> * 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
next prev parent reply other threads:[~2020-03-03 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 0:56 Rajat Jain
2020-03-03 0:56 ` [PATCH 2/2] Input: Allocate keycode for SNIP key Rajat Jain
2020-03-03 8:15 ` Bastien Nocera [this message]
2020-03-03 23:59 ` [PATCH 1/2] Input: Add keycodes for keyboard backlight control Rajat Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe4e0010826d4d18843b148dc088c2b01c7e2072.camel@hadess.net \
--to=hadess@hadess.net \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@google.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajatja@google.com \
--cc=rajatxjain@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®