linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	Gabriele Mazzotta <gabriele.mzt@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Side effect of pressing special keys
Date: Wed, 3 Dec 2014 13:46:13 +0100	[thread overview]
Message-ID: <201412031346.13297@pali> (raw)
In-Reply-To: <20141203124042.GA504@amd>

[-- Attachment #1: Type: Text/Plain, Size: 795 bytes --]

On Wednesday 03 December 2014 13:40:42 Pavel Machek wrote:
> On Sun 2014-11-23 14:41:17, Pali Rohár wrote:
> > 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)
> 
> We should not really report that as a "key" to userspace. We
> might want to report that rfkill state changed....
> 							Pavel

Ok, and what about KEY_KBDILLUMTOGGLE when bios also handle 
keyboard backlight level? Should be this key filtered too?

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-12-03 12:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 13:41 Side effect of pressing special keys Pali Rohár
2014-12-03 12:40 ` Pavel Machek
2014-12-03 12:46   ` Pali Rohár [this message]
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=201412031346.13297@pali \
    --to=pali.rohar@gmail.com \
    --cc=gabriele.mzt@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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).