From: "Pali Rohár" <pali.rohar@gmail.com>
To: Gabriele Mazzotta <gabriele.mzt@gmail.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Pavel Machek <pavel@ucw.cz>,
linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Side effect of pressing special keys
Date: Wed, 3 Dec 2014 14:40:50 +0100 [thread overview]
Message-ID: <201412031440.50755@pali> (raw)
In-Reply-To: <2102451.ffMsF9xTEG@xps13>
[-- Attachment #1: Type: Text/Plain, Size: 1520 bytes --]
On Wednesday 03 December 2014 14:38:15 Gabriele Mazzotta wrote:
> On Wednesday 03 December 2014 14:24:11 Pali Rohár wrote:
> > On Wednesday 03 December 2014 14:12:54 Henrique de Moraes
> >
> > Holschuh wrote:
> > > On Wed, 03 Dec 2014, Pali Rohár wrote:
> > > > Ok, and what about KEY_KBDILLUMTOGGLE when bios also
> > > > handle keyboard backlight level? Should be this key
> > > > filtered too?
> > >
> > > IME, heck yes.
> > >
> > > If you ever make the mistake of sending to userspace
> > > something the BIOS/kernel already reacted to, they will
> > > find a way to loop it back to you and cause all sort of
> > > issues.
> >
> > Ok, I think same. In KDE4 I see some loop/noop operation
> > when new dell keyboard backlight driver is used. Key
> > KEY_KBDILLUMTOGGLE cause that BIOS change brightness and
> > also KDE4 see it and change it too...
> >
> > Similar problem there is with KEY_WLAN and NetworkManager.
> >
> > Gabriele, can you create patch which disable both KEY_WLAN
> > and KEY_KBDILLUMTOGGLE in dell-wmi.c driver?
>
> KEY_KBDILLUMTOGGLE is actually disabled already, but KEY_WLAN
> (which I guess it should changed to KEY_RFKILL now that it
> exists) isn't, so I will submit a patch. The comment above it
> in dell-wmi.c makes me think that for all the systems the
> BIOS does everything and not only mine.
>
> Gabriele
KEY_KBDILLUMTOGGLE is not disabled for sure. I see it in log from
input-events program.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2014-12-03 13:40 UTC|newest]
Thread overview: 10+ 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:40 ` Pavel Machek
2014-12-03 12:46 ` Pali Rohár
2014-12-03 13:12 ` Henrique de Moraes Holschuh
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:38 ` Gabriele Mazzotta
2014-12-03 13:40 ` Pali Rohár [this message]
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=201412031440.50755@pali \
--to=pali.rohar@gmail.com \
--cc=gabriele.mzt@gmail.com \
--cc=hmh@hmh.eng.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.