Need a bit of help with KEYBOARD_KEY_xx hwdb entries

[grawity@xxxxxxxxx (Mantas Mikulėnas)]

On Sun, Apr 29, 2018 at 6:49 PM Sam Morris <sam at robots.org.uk> wrote:

> Pressing the brightness keys on my Dell Vostro 1520 results in events
> coming from both the atkbd and the acpi-video input devices, resulting
> in double-stepped brightness changes. Based on
> I'm trying to arrange for the brightness key events for the atkbd
> device in my laptop (Dell Vostro 1520) to be ignored, as the acpi-video
> input device also generates them, resulting in double-stepped
> brightness changes. Based on the output of libinput-debug-events:
>
> -event0   KEYBOARD_KEY      +5.62s      KEY_BRIGHTNESSDOWN (224) pressed
>  event0   KEYBOARD_KEY      +5.62s      KEY_BRIGHTNESSDOWN (224) released
> -event0   KEYBOARD_KEY      +9.61s      KEY_BRIGHTNESSUP (225) pressed
>  event0   KEYBOARD_KEY      +9.61s      KEY_BRIGHTNESSUP (225) released
>
> I've got the following:
>
> # Dell Vostro 1520
> evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDellInc.:pnVostro1520:pvr*
>  KEYBOARD_KEY_e0=unknown # Brightness Down, also emitted by acpi-video,
> ignore
>  KEYBOARD_KEY_e1=unknown # Brightness Up, also emitted by acpi-video,
> ignore
>
> ... which has applied OK:
>
> $ /sbin/udevadm info --path=/sys/class/input/event0 | grep
> KEYBOARD_KEY_e[01]
> E: KEYBOARD_KEY_e0=unknown
> E: KEYBOARD_KEY_e1=unknown
>

Wait, I thought the mappings are "scan code â?? evdev code"? 224/225 as shown
by libinput-debug-events would be the evdev codes (i.e. the mapping *result*),
not scan codes.

-- 
Mantas MikulÄ?nas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180430/e05d07d6/attachment.html>