From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Joe Wu <joewu@msi.corp-partner.google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Xiang wangx <wangxiang@cdjrlc.com>,
linux-input@vger.kernel.org, Derek Huang <derekhuang@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Benson Leung <bleung@chromium.org>,
Daisuke Nojiri <dnojiri@chromium.org>,
Prashant Malani <pmalani@chromium.org>,
Furquan Shaikh <furquan@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
chrome-platform@lists.linux.dev,
Douglas Anderson <dianders@chromium.org>,
"Dustin L . Howett" <dustin@howett.net>,
Guenter Roeck <groeck@chromium.org>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: Re: [PATCH] cros_ec_keyb: Add 3 buttons for monitor function
Date: Thu, 15 Dec 2022 14:01:25 -0800 [thread overview]
Message-ID: <Y5uZNVzEgsKzlPD0@google.com> (raw)
In-Reply-To: <20221215061550.18993-1-joewu@msi.corp-partner.google.com>
Hi Joe,
On Thu, Dec 15, 2022 at 02:15:50PM +0800, Joe Wu wrote:
> This patch is to add extra 3 buttons: 'brightness up',
> 'brightness down' and 'leave PC(cros) mode' to support
> monitor navigation function.
I understand "brightness up" and "brightness down" but I have no idea
what "leave PC(cros) mode" means. I also do not think we should be
abusing F13 for this.
Thanks.
>
> Signed-off-by: Joe Wu <joewu@msi.corp-partner.google.com>
>
> ---
>
> drivers/input/keyboard/cros_ec_keyb.c | 15 +++++++++++++++
> include/linux/platform_data/cros_ec_commands.h | 3 +++
> 2 files changed, 18 insertions(+)
>
> diff --git a/drivers/input/keyboard/cros_ec_keyb.c b/drivers/input/keyboard/cros_ec_keyb.c
> index c14136b733a9..bf1cf0b782d2 100644
> --- a/drivers/input/keyboard/cros_ec_keyb.c
> +++ b/drivers/input/keyboard/cros_ec_keyb.c
> @@ -100,6 +100,21 @@ static const struct cros_ec_bs_map cros_ec_keyb_bs[] = {
> .code = KEY_VOLUMEDOWN,
> .bit = EC_MKBP_VOL_DOWN,
> },
> + {
> + .ev_type = EV_KEY,
> + .code = KEY_BRIGHTNESSUP,
> + .bit = EC_MKBP_BRI_UP,
> + },
> + {
> + .ev_type = EV_KEY,
> + .code = KEY_BRIGHTNESSDOWN,
> + .bit = EC_MKBP_BRI_DOWN,
> + },
> + {
> + .ev_type = EV_KEY,
> + .code = KEY_F13,
> + .bit = EC_MKBP_CROS_LEAVE,
> + },
>
> /* Switches */
> {
> diff --git a/include/linux/platform_data/cros_ec_commands.h b/include/linux/platform_data/cros_ec_commands.h
> index 5744a2d746aa..79218da8a8cb 100644
> --- a/include/linux/platform_data/cros_ec_commands.h
> +++ b/include/linux/platform_data/cros_ec_commands.h
> @@ -3471,6 +3471,9 @@ struct ec_response_get_next_event_v1 {
> #define EC_MKBP_VOL_UP 1
> #define EC_MKBP_VOL_DOWN 2
> #define EC_MKBP_RECOVERY 3
> +#define EC_MKBP_BRI_UP 4
> +#define EC_MKBP_BRI_DOWN 5
> +#define EC_MKBP_CROS_LEAVE 6
>
> /* Switches */
> #define EC_MKBP_LID_OPEN 0
> --
> 2.17.1
>
--
Dmitry
next prev parent reply other threads:[~2022-12-15 22:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 6:15 [PATCH] cros_ec_keyb: Add 3 buttons for monitor function Joe Wu
2022-12-15 22:01 ` Dmitry Torokhov [this message]
2022-12-16 1:36 ` joewu(吳仲振)
2022-12-16 19:19 ` Dmitry Torokhov
2022-12-15 22:58 ` Prashant Malani
2022-12-16 1:17 ` joewu(吳仲振)
2022-12-20 8:02 Joe Wu
2022-12-21 7:28 ` Greg Kroah-Hartman
2022-12-22 1:50 ` joewu(吳仲振)
2022-12-22 5:51 ` Greg Kroah-Hartman
2022-12-22 2:15 Joe Wu
2022-12-22 6:07 ` Greg Kroah-Hartman
2022-12-22 6:34 ` joewu(吳仲振)
2022-12-22 6:08 ` Greg Kroah-Hartman
2022-12-22 6:39 Joe Wu
2022-12-22 6:49 ` Greg Kroah-Hartman
2023-01-20 11:26 ` Greg Kroah-Hartman
2023-01-20 17:24 ` Dmitry Torokhov
2023-01-21 7:26 ` Greg Kroah-Hartman
2023-01-24 6:14 ` Dmitry Torokhov
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=Y5uZNVzEgsKzlPD0@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=derekhuang@google.com \
--cc=dianders@chromium.org \
--cc=dnojiri@chromium.org \
--cc=dustin@howett.net \
--cc=furquan@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=gustavoars@kernel.org \
--cc=joewu@msi.corp-partner.google.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=sebastian.reichel@collabora.com \
--cc=swboyd@chromium.org \
--cc=tzungbi@kernel.org \
--cc=wangxiang@cdjrlc.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;
as well as URLs for NNTP newsgroup(s).