All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gergo Koteles <soyer@irl.hu>
To: "Ike Panhc" <ike.pan@canonical.com>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	Gergo Koteles <soyer@irl.hu>
Subject: [PATCH v2 0/2] map Fn + R key on newer Lenovo Yogas and Legions
Date: Sun, 10 Mar 2024 12:31:40 +0100	[thread overview]
Message-ID: <cover.1710065750.git.soyer@irl.hu> (raw)

Hi All,

This patch series adds a new KEY_REFRESH_RATE_TOGGLE input event code 
and maps the Fn + R key to it in the ideapad-laptop driver.

It affects two WMI keycodes. I couldn't try the 0x0a.

Regards,
Gergo

Changes in v2:
 - use KEY_REFRESH_RATE_TOGGLE instead of KEY_FN_R

[1]: https://lore.kernel.org/all/cover.1708399689.git.soyer@irl.hu/

Gergo Koteles (2):
  Input: allocate keycode for Display refresh rate toggle
  platform/x86: ideapad-laptop: map Fn + R key to
    KEY_REFRESH_RATE_TOGGLE

 drivers/platform/x86/ideapad-laptop.c  | 4 ++--
 include/uapi/linux/input-event-codes.h | 1 +
 2 files changed, 3 insertions(+), 2 deletions(-)


base-commit: b401b621758e46812da61fa58a67c3fd8d91de0d
prerequisite-patch-id: 66a1ec71f181c6468a8226430af7ee917f40138a
-- 
2.44.0


             reply	other threads:[~2024-03-10 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10 11:31 Gergo Koteles [this message]
2024-03-10 11:31 ` [PATCH v2 1/2] Input: allocate keycode for Display refresh rate toggle Gergo Koteles
2024-03-10 21:34   ` Dmitry Torokhov
2024-03-10 11:31 ` [PATCH v2 2/2] platform/x86: ideapad-laptop: map Fn + R key to KEY_REFRESH_RATE_TOGGLE Gergo Koteles
2024-03-11 13:28 ` [PATCH v2 0/2] map Fn + R key on newer Lenovo Yogas and Legions Ilpo Järvinen
2024-03-12 11:01   ` Ilpo Järvinen

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=cover.1710065750.git.soyer@irl.hu \
    --to=soyer@irl.hu \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ike.pan@canonical.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.