From: Giedrius Statkevicius <giedrius.statkevicius@gmail.com>
To: linux-input@vger.kernel.org
Subject: Hp 3d driveguard seems to be sending events through the keyboard bus - should atkbd be modified to ignore that?
Date: Thu, 16 Oct 2014 19:05:01 +0300 [thread overview]
Message-ID: <543FECAD.5030104@gmail.com> (raw)
Hello,
In some hp laptops there is a functionality called hp 3d driverguard
which is basically a accelerometer that detects free fall. It seems
that on some laptops a keyboard button press event is generated when
accelerometer's values change and ofc the scan code is not recognized
by atkbd (and it shouldn't be as it's not a real key). The result of
this is that the system log gets filled with these messages:
[ 9163.578181] atkbd serio0: Unknown key pressed (translated set 2, code 0xa8 on isa0060/serio0).
[ 9163.578189] atkbd serio0: Use 'setkeycodes e028 <keycode>' to make it known.
The range of scan codes seem to be from 0xa5 to 0xa8. In my opinion,
these scan codes on hp laptops with this future should definitely be
ignored because they are handled by the 'hp_accel' driver. For some
reason, the accelerometer sends the events through the keyboard bus too.
I've filled a bug report here:
https://bugzilla.kernel.org/show_bug.cgi?id=84941
What does everyone else think about ignoring these scan codes for
laptops with this particular feature?
next reply other threads:[~2014-10-16 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 16:05 Giedrius Statkevicius [this message]
2014-10-16 23:11 ` Hp 3d driveguard seems to be sending events through the keyboard bus - should atkbd be modified to ignore that? Dmitry Torokhov
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=543FECAD.5030104@gmail.com \
--to=giedrius.statkevicius@gmail.com \
--cc=linux-input@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).