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>,
"Philipp Jungkamp" <p.jungkamp@gmx.net>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Gergo Koteles <soyer@irl.hu>
Subject: [PATCH 0/2] map Fn + R key on newer Yogas and Legions
Date: Tue, 20 Feb 2024 04:39:34 +0100 [thread overview]
Message-ID: <cover.1708399689.git.soyer@irl.hu> (raw)
Hi All,
This patch series adds a new KEY_FN_R input event code and map the
Fn + R key to it in the ideapad-laptop driver.
It affects two WMI keycodes and I couldn't try the 0x0a, but I couldn't
find any indication that the refresh rate toggle should not be Fn + R.
Regards,
Gergo
Gergo Koteles (2):
Input: allocate keycode for Fn + R
platform/x86: ideapad-laptop: map Fn + R key to KEY_FN_R
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.43.2
next reply other threads:[~2024-02-20 3:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 3:39 Gergo Koteles [this message]
2024-02-20 3:39 ` [PATCH 1/2] Input: allocate keycode for Fn + R Gergo Koteles
2024-02-20 3:39 ` [PATCH 2/2] platform/x86: ideapad-laptop: map Fn + R key to KEY_FN_R Gergo Koteles
2024-02-26 13:27 ` [PATCH 0/2] map Fn + R key on newer Yogas and Legions Ilpo Järvinen
2024-03-10 1:39 ` Dmitry Torokhov
2024-03-11 10:53 ` Ilpo Järvinen
2024-03-11 18:45 ` Dmitry Torokhov
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.1708399689.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=p.jungkamp@gmx.net \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).