Hp 3d driveguard seems to be sending events through the keyboard bus - should atkbd be modified to ignore that?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux