linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcos Alano <marcoshalano@gmail.com>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Add keycode for performance mode keys
Date: Sun, 3 Aug 2025 09:22:20 -0300	[thread overview]
Message-ID: <2e1b645c-8374-42e4-94ae-826abb4fb138@gmail.com> (raw)
In-Reply-To: <20250509193708.2190586-1-marcoshalano@gmail.com>

@Dmitry,

Could you check this patch, please?

Thanks,


On 09/05/2025 16:37, Marcos Alano wrote:
> Alienware calls this key "Performance Boost". Dell calls it "G-Mode".
> 
> The goal is to have a specific keycode to detect when this key is
> pressed, so userspace can act upon it and do what have to do, usually
> starting the power profile for performance.
> 
> Signed-off-by: Marcos Alano <marcoshalano@gmail.com>
> ---
>   include/uapi/linux/input-event-codes.h | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h
> index 5a199f3d4a26..f410394cd769 100644
> --- a/include/uapi/linux/input-event-codes.h
> +++ b/include/uapi/linux/input-event-codes.h
> @@ -765,6 +765,11 @@
>   #define KEY_KBD_LCD_MENU4		0x2bb
>   #define KEY_KBD_LCD_MENU5		0x2bc
>   
> +/* Performance Boost key (Alienware)
> + * G-Mode key (Dell)
> + */
> +#define KEY_PERFORMANCE                 0x2bd
> +
>   #define BTN_TRIGGER_HAPPY		0x2c0
>   #define BTN_TRIGGER_HAPPY1		0x2c0
>   #define BTN_TRIGGER_HAPPY2		0x2c1

-- 
Marcos Alano


  reply	other threads:[~2025-08-03 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 19:37 [PATCH] Add keycode for performance mode keys Marcos Alano
2025-08-03 12:22 ` Marcos Alano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-09 19:34 Marcos Alano

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=2e1b645c-8374-42e4-94ae-826abb4fb138@gmail.com \
    --to=marcoshalano@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    /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).