[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200609154938.udo7mn7ka7z7pr6c@pali>
Date: Tue, 9 Jun 2020 17:49:38 +0200
From: Pali Rohár <pali@...nel.org>
To: Mario.Limonciello@...l.com, Sebastian Reichel <sre@...nel.org>
Cc: y.linux@...itcher.com, hdegoede@...hat.com,
linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org,
linux-pm@...r.kernel.org, mjg59@...f.ucam.org
Subject: Re: [PATCH 2/3] platform/x86: dell-wmi: add new keymap type 0x0012
On Monday 08 June 2020 20:36:58 Mario.Limonciello@...l.com wrote:
> Can you please comment here how you would like to see events like this should come
> through to userspace?
>
> * Wrong power adapter (you have X and should have Y)
> * You have plugged a dock into the wrong port
> * Fn-lock mode
In my opinion, Fn-lock mode is related to input subsystem and should be
probably reported via input device. For a user, fn-lock is similar like
caps-lock, scroll-lock or num-lock. Also fn-lock is provided by other
laptops and therefore I would expect that kernel provide fn-lock state
for all laptops (thinkpad / latitude / ...) via same interface. And not
via dell-specific interface or general-vendor-message interface.
Wrong power adapter sounds like something related to power subsystem.
Adding Sebastian to the loop, maybe he can provide some useful ideas
about it.
And plugged dock into wrong port. This is probably dell-specific event
and some interface for "vendor" messages from kernel to userspace would
be needed to deliver such things.
Powered by blists - more mailing lists