2018-06-14 11:54:52 +10:00
|
|
|
# Do not edit this file, it will be overwritten on update
|
2025-12-15 14:30:10 +01:00
|
|
|
|
|
|
|
|
[HP Chromebook 14]
|
|
|
|
|
MatchName=*Cypress APA Trackpad *cyapa*
|
|
|
|
|
MatchDMIModalias=dmi:*svnHewlett-Packard*:pnFalco*
|
|
|
|
|
AttrPressureRange=12:8
|
|
|
|
|
|
2018-10-19 15:27:20 +10:00
|
|
|
# Claims to have double/tripletap but doesn't actually send it
|
|
|
|
|
# https://bugs.freedesktop.org/show_bug.cgi?id=98538
|
Implement a quirks system to replace the udev property parsing
Previously, we had all extra device information ("This is an Apple Touchpad",
"This touchpad causes pointer jumps", etc.) in the udev hwdb. The problem with
the hwdb is that updating it is nontrivial for the average user and debugging
when things go wrong is even harder. Plus, the hwdb has a matching scheme that
is unpredictable unless one is familiar with the implementation.
This patch set moves the hwdb entries into .ini style text files, with a
simple line-based parser. A new libinput list-quirks tool can list the quirks
applied to any given device, in --verbose mode it prints all matches as they
apply or not apply.
The data files are currently unused by libinput, that comes in a later patch.
They're installed though, the defaults point to the /usr/share/libinput
directory and for *temporary* local overrides the single file
/etc/libinput/local-overrides.quirks.
Failure to parse any file is a hard failure for the quirks system, but if the
local override file doesn't exist that's fine.
THIS IS NOT A CONFIGURATION INTERFACE! None of these settings are exposed via
the libinput_device_config_* calls. There is no API guarantee for these files,
think of them as source code.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2018-05-21 14:28:53 +10:00
|
|
|
[HP Compaq 6910p]
|
|
|
|
|
MatchName=*SynPS/2 Synaptics TouchPad
|
|
|
|
|
MatchDMIModalias=dmi:*svnHewlett-Packard:*pnHPCompaq6910p*
|
quirks: allow overriding of AttrEventCode and AttrInputProp
This switches the quirk from AttrEventCodeEnable/Disable to just
AttrEventCode with a +/- prefix for each entry.
This switches the quirk from AttrInputPropEnable/Disable to just
AttrInputProp with a +/- prefix for each entry.
Previously, both event codes and input props would only apply the
last-matching section entry for a device. Furthermore, an earlier Disable entry
would take precedence over a later Enable entry. For example, a set of
sections with these lines *should* enable left, right and middle:
[first]
AttrEventCodeEnable=BTN_LEFT;BTN_RIGHT;BTN_MIDDLE
[second]
AttrEventCodeDisable=BTN_RIGHT
[third]
AttrEventCodeEnable=BTN_LEFT;BTN_RIGHT;
Alas: the first line was effectively ignored (quirks only returned the
last-matching one, i.e. the one from "third"). And due to implementation
details in evdev.c, the Disable attribute was processed after Enable,
i.e. the device was enabled for left + right and then disabled for
right. As a result, the device only had BTN_LEFT enabled.
Fix this by changing the attribute to carry both enable/disable
information and merging the commands together.
Internally, all quirks matching a device are simply ref'd into an array
in the struct quirks. The applied value is simply the last entry in the
array corresponding to our quirk.
For AttrEventCode and AttrInputProp instead do this:
- switch them to a tuple with the code as first entry and a boolean
enable/disable as second entry
- if the struct quirk already has an entry for either, append the more
recent one to the existing entry (instead of creating a new entry in
the array). This way we have all entries that match and in-order of
precedence - i.e. we can process them left-to-right to end up
with the right state.
Fixes: https://gitlab.freedesktop.org/libinput/libinput/-/issues/821
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2022-11-15 13:53:43 +10:00
|
|
|
AttrEventCode=-BTN_TOOL_DOUBLETAP;-BTN_TOOL_TRIPLETAP;
|
Implement a quirks system to replace the udev property parsing
Previously, we had all extra device information ("This is an Apple Touchpad",
"This touchpad causes pointer jumps", etc.) in the udev hwdb. The problem with
the hwdb is that updating it is nontrivial for the average user and debugging
when things go wrong is even harder. Plus, the hwdb has a matching scheme that
is unpredictable unless one is familiar with the implementation.
This patch set moves the hwdb entries into .ini style text files, with a
simple line-based parser. A new libinput list-quirks tool can list the quirks
applied to any given device, in --verbose mode it prints all matches as they
apply or not apply.
The data files are currently unused by libinput, that comes in a later patch.
They're installed though, the defaults point to the /usr/share/libinput
directory and for *temporary* local overrides the single file
/etc/libinput/local-overrides.quirks.
Failure to parse any file is a hard failure for the quirks system, but if the
local override file doesn't exist that's fine.
THIS IS NOT A CONFIGURATION INTERFACE! None of these settings are exposed via
the libinput_device_config_* calls. There is no API guarantee for these files,
think of them as source code.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2018-05-21 14:28:53 +10:00
|
|
|
|
2018-10-19 15:27:20 +10:00
|
|
|
# Claims to have double/tripletap but doesn't actually send it
|
|
|
|
|
# https://bugzilla.redhat.com/show_bug.cgi?id=1351285 and
|
Implement a quirks system to replace the udev property parsing
Previously, we had all extra device information ("This is an Apple Touchpad",
"This touchpad causes pointer jumps", etc.) in the udev hwdb. The problem with
the hwdb is that updating it is nontrivial for the average user and debugging
when things go wrong is even harder. Plus, the hwdb has a matching scheme that
is unpredictable unless one is familiar with the implementation.
This patch set moves the hwdb entries into .ini style text files, with a
simple line-based parser. A new libinput list-quirks tool can list the quirks
applied to any given device, in --verbose mode it prints all matches as they
apply or not apply.
The data files are currently unused by libinput, that comes in a later patch.
They're installed though, the defaults point to the /usr/share/libinput
directory and for *temporary* local overrides the single file
/etc/libinput/local-overrides.quirks.
Failure to parse any file is a hard failure for the quirks system, but if the
local override file doesn't exist that's fine.
THIS IS NOT A CONFIGURATION INTERFACE! None of these settings are exposed via
the libinput_device_config_* calls. There is no API guarantee for these files,
think of them as source code.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2018-05-21 14:28:53 +10:00
|
|
|
[HP Compaq 8510w]
|
|
|
|
|
MatchName=*SynPS/2 Synaptics TouchPad
|
|
|
|
|
MatchDMIModalias=dmi:*svnHewlett-Packard:*pnHPCompaq8510w*
|
quirks: allow overriding of AttrEventCode and AttrInputProp
This switches the quirk from AttrEventCodeEnable/Disable to just
AttrEventCode with a +/- prefix for each entry.
This switches the quirk from AttrInputPropEnable/Disable to just
AttrInputProp with a +/- prefix for each entry.
Previously, both event codes and input props would only apply the
last-matching section entry for a device. Furthermore, an earlier Disable entry
would take precedence over a later Enable entry. For example, a set of
sections with these lines *should* enable left, right and middle:
[first]
AttrEventCodeEnable=BTN_LEFT;BTN_RIGHT;BTN_MIDDLE
[second]
AttrEventCodeDisable=BTN_RIGHT
[third]
AttrEventCodeEnable=BTN_LEFT;BTN_RIGHT;
Alas: the first line was effectively ignored (quirks only returned the
last-matching one, i.e. the one from "third"). And due to implementation
details in evdev.c, the Disable attribute was processed after Enable,
i.e. the device was enabled for left + right and then disabled for
right. As a result, the device only had BTN_LEFT enabled.
Fix this by changing the attribute to carry both enable/disable
information and merging the commands together.
Internally, all quirks matching a device are simply ref'd into an array
in the struct quirks. The applied value is simply the last entry in the
array corresponding to our quirk.
For AttrEventCode and AttrInputProp instead do this:
- switch them to a tuple with the code as first entry and a boolean
enable/disable as second entry
- if the struct quirk already has an entry for either, append the more
recent one to the existing entry (instead of creating a new entry in
the array). This way we have all entries that match and in-order of
precedence - i.e. we can process them left-to-right to end up
with the right state.
Fixes: https://gitlab.freedesktop.org/libinput/libinput/-/issues/821
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2022-11-15 13:53:43 +10:00
|
|
|
AttrEventCode=-BTN_TOOL_DOUBLETAP;-BTN_TOOL_TRIPLETAP;
|
Implement a quirks system to replace the udev property parsing
Previously, we had all extra device information ("This is an Apple Touchpad",
"This touchpad causes pointer jumps", etc.) in the udev hwdb. The problem with
the hwdb is that updating it is nontrivial for the average user and debugging
when things go wrong is even harder. Plus, the hwdb has a matching scheme that
is unpredictable unless one is familiar with the implementation.
This patch set moves the hwdb entries into .ini style text files, with a
simple line-based parser. A new libinput list-quirks tool can list the quirks
applied to any given device, in --verbose mode it prints all matches as they
apply or not apply.
The data files are currently unused by libinput, that comes in a later patch.
They're installed though, the defaults point to the /usr/share/libinput
directory and for *temporary* local overrides the single file
/etc/libinput/local-overrides.quirks.
Failure to parse any file is a hard failure for the quirks system, but if the
local override file doesn't exist that's fine.
THIS IS NOT A CONFIGURATION INTERFACE! None of these settings are exposed via
the libinput_device_config_* calls. There is no API guarantee for these files,
think of them as source code.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2018-05-21 14:28:53 +10:00
|
|
|
|
2025-12-15 14:30:10 +01:00
|
|
|
[HP Elite x2 1013 G3 Keyboard]
|
|
|
|
|
MatchUdevType=keyboard
|
|
|
|
|
MatchBus=ps2
|
|
|
|
|
MatchDMIModalias=dmi:*svnHP:pnHPElitex21013G3:*
|
|
|
|
|
AttrKeyboardIntegration=external
|
Implement a quirks system to replace the udev property parsing
Previously, we had all extra device information ("This is an Apple Touchpad",
"This touchpad causes pointer jumps", etc.) in the udev hwdb. The problem with
the hwdb is that updating it is nontrivial for the average user and debugging
when things go wrong is even harder. Plus, the hwdb has a matching scheme that
is unpredictable unless one is familiar with the implementation.
This patch set moves the hwdb entries into .ini style text files, with a
simple line-based parser. A new libinput list-quirks tool can list the quirks
applied to any given device, in --verbose mode it prints all matches as they
apply or not apply.
The data files are currently unused by libinput, that comes in a later patch.
They're installed though, the defaults point to the /usr/share/libinput
directory and for *temporary* local overrides the single file
/etc/libinput/local-overrides.quirks.
Failure to parse any file is a hard failure for the quirks system, but if the
local override file doesn't exist that's fine.
THIS IS NOT A CONFIGURATION INTERFACE! None of these settings are exposed via
the libinput_device_config_* calls. There is no API guarantee for these files,
think of them as source code.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2018-05-21 14:28:53 +10:00
|
|
|
|
2025-12-15 14:30:10 +01:00
|
|
|
[HP Elite x2 1013 G3 Tablet Mode Switch]
|
|
|
|
|
MatchName=*Intel Virtual Button*
|
|
|
|
|
MatchDMIModalias=dmi:*svnHP:pnHPElitex21013G3:*
|
|
|
|
|
ModelTabletModeSwitchUnreliable=1
|
Implement a quirks system to replace the udev property parsing
Previously, we had all extra device information ("This is an Apple Touchpad",
"This touchpad causes pointer jumps", etc.) in the udev hwdb. The problem with
the hwdb is that updating it is nontrivial for the average user and debugging
when things go wrong is even harder. Plus, the hwdb has a matching scheme that
is unpredictable unless one is familiar with the implementation.
This patch set moves the hwdb entries into .ini style text files, with a
simple line-based parser. A new libinput list-quirks tool can list the quirks
applied to any given device, in --verbose mode it prints all matches as they
apply or not apply.
The data files are currently unused by libinput, that comes in a later patch.
They're installed though, the defaults point to the /usr/share/libinput
directory and for *temporary* local overrides the single file
/etc/libinput/local-overrides.quirks.
Failure to parse any file is a hard failure for the quirks system, but if the
local override file doesn't exist that's fine.
THIS IS NOT A CONFIGURATION INTERFACE! None of these settings are exposed via
the libinput_device_config_* calls. There is no API guarantee for these files,
think of them as source code.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2018-05-21 14:28:53 +10:00
|
|
|
|
2025-12-15 14:30:10 +01:00
|
|
|
[HP Elite x2 1013 G3 Touchpad]
|
|
|
|
|
MatchUdevType=touchpad
|
|
|
|
|
MatchBus=usb
|
|
|
|
|
MatchVendor=0x044E
|
|
|
|
|
MatchProduct=0x1221
|
|
|
|
|
AttrTPKComboLayout=below
|
|
|
|
|
|
|
|
|
|
# The HP OmniBook Ultra Flip Laptop 14-fh0xxx's custom Intel ISH firmware
|
|
|
|
|
# filters out events from its builtin keyboard and touchpad when the hinge is
|
|
|
|
|
# opened little more than 180 degrees but toggles tablet-mode when it's opened
|
|
|
|
|
# little less than 180 degrees.
|
|
|
|
|
# Do not suspend the keyboard and touchpad to let use the device in flat
|
|
|
|
|
# position and also give consistency with some keyboard keys controlled by the
|
|
|
|
|
# Video Bus device (brightness down/up), the HP WMI hotkeys device (mic mute and
|
|
|
|
|
# hp hubs launcher key) and the backlight getting on and off by the firmware at
|
|
|
|
|
# the same time it enables disables the input.
|
|
|
|
|
# This one is for the keyboard and...
|
|
|
|
|
[HP OmniBook Ultra Flip Laptop 14-fh0xxx Keyboard]
|
2025-12-15 14:34:39 +01:00
|
|
|
MatchBus=ps2
|
|
|
|
|
MatchUdevType=keyboard
|
|
|
|
|
MatchDMIModalias=dmi:*:svnHP:pnHPOmniBookUltraFlipLaptop14-fh0xxx:*
|
2020-05-15 21:17:36 +02:00
|
|
|
ModelTabletModeNoSuspend=1
|
|
|
|
|
|
2025-12-15 14:30:10 +01:00
|
|
|
# ...this one is for the touchpad.
|
|
|
|
|
[HP OmniBook Ultra Flip Laptop 14-fh0xxx Touchpad]
|
2025-12-15 14:34:39 +01:00
|
|
|
MatchBus=i2c
|
|
|
|
|
MatchVendor=0x06CB
|
|
|
|
|
MatchProduct=0xCFD2
|
|
|
|
|
MatchUdevType=touchpad
|
|
|
|
|
MatchDMIModalias=dmi:*:svnHP:pnHPOmniBookUltraFlipLaptop14-fh0xxx:*
|
2025-12-15 14:30:10 +01:00
|
|
|
ModelTabletModeNoSuspend=1
|
|
|
|
|
|
|
|
|
|
[HP Pavilion dmi4]
|
|
|
|
|
MatchName=*SynPS/2 Synaptics TouchPad
|
|
|
|
|
MatchDMIModalias=dmi:*svnHewlett-Packard:*pnHPPaviliondm4NotebookPC*
|
|
|
|
|
ModelHPPavilionDM4Touchpad=1
|
|
|
|
|
|
2022-02-03 01:28:55 +00:00
|
|
|
[HP Spectre x360 Convertible 15-bl000]
|
|
|
|
|
MatchName=AT Translated Set 2 keyboard
|
|
|
|
|
MatchDMIModalias=dmi:*:svnHP:pnHPSpectrex360Convertible15-bl0XX:*
|
|
|
|
|
ModelTabletModeNoSuspend=1
|
|
|
|
|
|
2020-08-27 19:52:34 +02:00
|
|
|
[HP Spectre x360 Convertible 15-bl1xx]
|
2018-11-23 15:10:15 -06:00
|
|
|
MatchUdevType=touchpad
|
|
|
|
|
MatchName=*SynPS/2 Synaptics TouchPad
|
|
|
|
|
MatchDMIModalias=dmi:*svnHP:pnHPSpectrex360Convertible15-bl1XX:*
|
|
|
|
|
AttrPressureRange=55:40
|
|
|
|
|
AttrThumbPressureThreshold=90
|
|
|
|
|
AttrPalmPressureThreshold=100
|
2019-08-30 15:09:01 +00:00
|
|
|
|
2020-08-27 19:52:34 +02:00
|
|
|
[HP Spectre x360 Convertible 15-ch0xx]
|
2019-11-25 02:02:55 +00:00
|
|
|
MatchUdevType=touchpad
|
|
|
|
|
MatchName=*SynPS/2 Synaptics TouchPad
|
|
|
|
|
MatchDMIModalias=dmi:*svnHP:pnHPSpectrex360Convertible15-ch0xx:*
|
|
|
|
|
AttrThumbPressureThreshold=90
|
|
|
|
|
AttrPalmPressureThreshold=100
|
|
|
|
|
|
2023-07-31 13:24:57 +02:00
|
|
|
# The HP stream x360's embedded-controller filters out events form its builtin
|
|
|
|
|
# keyboard when in tablet-mode itself; and it has a volume up/down on the side.
|
|
|
|
|
# Do not suspend the keyboard when in tablet-mode so that the volume up/down
|
|
|
|
|
# button keeps working when in tablet-mode.
|
|
|
|
|
[HP Spectre x360 Convertible 15-ch0xx Tablet Mode Switch]
|
|
|
|
|
MatchName=AT Translated Set 2 keyboard
|
|
|
|
|
MatchDMIModalias=dmi:*svnHP:pnHPSpectrex360Convertible15-ch0xx:*
|
|
|
|
|
ModelTabletModeNoSuspend=1
|
2019-11-25 02:02:55 +00:00
|
|
|
|
2025-12-15 14:30:10 +01:00
|
|
|
# Touchpad is a clickpad but INPUT_PROP_BUTTONPAD is not set, see
|
|
|
|
|
# https://bugs.freedesktop.org/show_bug.cgi?id=97147
|
|
|
|
|
[HP Stream 11]
|
|
|
|
|
MatchName=SYN1EDE:00 06CB:7442*
|
|
|
|
|
MatchDMIModalias=dmi:*svnHewlett-Packard:pnHPStreamNotebookPC11*
|
|
|
|
|
AttrInputProp=+INPUT_PROP_BUTTONPAD
|
2025-08-29 23:53:58 +00:00
|
|
|
|
2025-12-15 14:30:10 +01:00
|
|
|
# The HP stream x360's embedded-controller filters out events form its builtin
|
|
|
|
|
# keyboard when in tablet-mode itself; and it has a capacitive home-button
|
|
|
|
|
# (windows logo) underneath its display which also sends PS/2 key-events.
|
|
|
|
|
# Do not suspend the keyboard when in tablet-mode so that the home button
|
|
|
|
|
# keeps working when in tablet-mode.
|
|
|
|
|
[HP Stream x360 11]
|
2025-08-29 23:53:58 +00:00
|
|
|
MatchName=AT Translated Set 2 keyboard
|
2025-12-15 14:30:10 +01:00
|
|
|
MatchDMIModalias=dmi:*:svnHewlett-Packard:pnHPStreamx360ConvertiblePC11:*
|
2025-08-29 23:53:58 +00:00
|
|
|
ModelTabletModeNoSuspend=1
|
|
|
|
|
|
2025-12-15 14:30:10 +01:00
|
|
|
[HP ZBook Studio G3]
|
|
|
|
|
MatchName=AlpsPS/2 ALPS GlidePoint
|
|
|
|
|
MatchDMIModalias=dmi:*svnHP:pnHPZBookStudioG3:*
|
|
|
|
|
ModelHPZBookStudioG3=1
|
