[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <db4dfc85-ce8b-4922-9558-670c3bb6eff2@kernel.org>
Date: Sat, 26 Apr 2025 18:44:54 -0500
From: Mario Limonciello <superm1@...nel.org>
To: Pavel Machek <pavel@....cz>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Shyam Sundar S K <Shyam-sundar.S-k@....com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Hans de Goede <hdegoede@...hat.com>,
"open list:INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN)..."
<linux-input@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>,
"open list:AMD PMF DRIVER" <platform-driver-x86@...r.kernel.org>,
Mario Limonciello <mario.limonciello@....com>, Armin Wolf <W_Armin@....de>
Subject: Re: [PATCH v4 1/2] Input: Add a Kconfig to emulate KEY_SCREENLOCK
with META + L
On 4/26/25 13:41, Pavel Machek wrote:
> Hi!
>
>>>> In the PC industry KEY_SCREENLOCK isn't used as frequently as it used
>>>> to be. Modern versions of Windows [1], GNOME and KDE support "META" + "L"
>>>> to lock the screen. Modern hardware [2] also sends this sequence of
>>>> events for keys with a silkscreen for screen lock.
>>>>
>>>> Introduced a new Kconfig option that will change KEY_SCREENLOCK when
>>>> emitted by driver to META + L.
>>>
>>> Fix gnome and kde, do not break kernel...
>>
>> I'm sorry; fix them to do what exactly? Switch to KEY_SCREENLOCK?
>>
>> That's going to break modern hardware lockscreen keys. They've all
>> obviously moved to META+L because that's what hardware today uses.
>
> Gnome / KDE should accept either META+L _or_ KEY_SCREENLOCK to do the
> screen locking, no?
>
This was actually the first path I looked down before I even started the
kernel patch direction for this problem.
GNOME doesn't support assigning more than one shortcut key for an action.
Powered by blists - more mailing lists