From: "Pali Rohár" <pali.rohar@gmail.com>
To: linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org
Cc: Gabriele Mazzotta <gabriele.mzt@gmail.com>, linux-kernel@vger.kernel.org
Subject: Side effect of pressing special keys
Date: Sun, 23 Nov 2014 14:41:17 +0100 [thread overview]
Message-ID: <201411231441.17592@pali> (raw)
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Hello,
pressing some keys on laptops could cause some side effects.
Example scenario 1:
Laptop has Fn key for enabling/disabling WIFI and when that key
is pressed BIOS is doing two things:
1) Switch hard rfkill state of WIFI
2) Report that Fn key was pressed to kernel
(either via i8042 bus or via ACPI/WMI)
Example scenario 2:
Another laptop has Fn key too, but BIOS does not change state of
hard rfkill. So system (kernel or userspace) is responsible for
interpreting what that Fn key means and call correct action (find
rfkill device for WIFI and soft block it).
And my questions are:
1) What should userspace do if some input device report that
KEY_WLAN or KEY_RFKILL was pressed?
2) Should kernel report to userspace that (on specific laptop)
has pressed key some side effect?
3) How to deal with existing userspace application which
interpret all pressed keys as described in example scenario 2
also on laptops from scenario 1? KDE4, NetworkManager, ... are
know to do that!
Note that this problem is not only about rfkill/wifi keys. Same
apply for keyboard brightness Fn keys and also for key
KEY_KBDILLUMTOGGLE (which toggle keyboard illumination level).
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2014-11-23 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 13:41 Pali Rohár [this message]
2014-12-03 12:40 ` Side effect of pressing special keys Pavel Machek
2014-12-03 12:46 ` Pali Rohár
2014-12-03 13:12 ` Henrique de Moraes Holschuh
2014-12-03 13:24 ` Pali Rohár
2014-12-03 13:38 ` Gabriele Mazzotta
2014-12-03 13:40 ` Pali Rohár
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=201411231441.17592@pali \
--to=pali.rohar@gmail.com \
--cc=gabriele.mzt@gmail.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 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).