rules.d/60-input-id.rules

# do not edit this file, it will be overwritten on update

ACTION=="remove", GOTO="id_input_end"

SUBSYSTEM=="input", ENV{ID_INPUT}=="", IMPORT{builtin}="input_id"
SUBSYSTEM=="input", IMPORT{builtin}="hwdb --subsystem=input --lookup-prefix=id-input:modalias:"

# id-input:<bus>:v<vid>p<pid>:name:<name>:*
KERNELS=="input*", ATTRS{id/bustype}=="0003", \
        IMPORT{builtin}="hwdb 'id-input:usb:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'", \
        GOTO="id_input_end"
KERNELS=="input*", ATTRS{id/bustype}=="0005", \
        IMPORT{builtin}="hwdb 'id-input:bluetooth:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'", \
        GOTO="id_input_end"
KERNELS=="input*", ATTRS{id/bustype}=="0018", \
        IMPORT{builtin}="hwdb 'id-input:i2c:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'", \
        GOTO="id_input_end"

LABEL="id_input_end"
rules: move input_id rule to a separate file This places the input_id call after the evdev hwdb calls. With this the hwdb fixups in evdev can affect the device capabilities assigned in input_id. Remove the ID_INPUT_KEY dependency in atkbd rule because it is now not assigned at this point. 2017-06-12 13:43:05 +02:00			`# do not edit this file, it will be overwritten on update`

			`ACTION=="remove", GOTO="id_input_end"`

			`SUBSYSTEM=="input", ENV{ID_INPUT}=="", IMPORT{builtin}="input_id"`
hwdb: add a hwdb file to override ID_INPUT assignments The input_id builtin assigns the various ID_INPUT based on the exported evdev bits. In some cases, the device may not have the properties required to label a device as one specific type but the physical form factor is clear. e.g. in the case of #7197 it's a tablet pad that does not have x/y axes which the kernel exports for pads for historical reasons. A custom override is needed, best to be solved with a hwdb entry. Related #7197 2017-10-30 10:42:29 +10:00			`SUBSYSTEM=="input", IMPORT{builtin}="hwdb --subsystem=input --lookup-prefix=id-input:modalias:"`
rules: move input_id rule to a separate file This places the input_id call after the evdev hwdb calls. With this the hwdb fixups in evdev can affect the device capabilities assigned in input_id. Remove the ID_INPUT_KEY dependency in atkbd rule because it is now not assigned at this point. 2017-06-12 13:43:05 +02:00
rules: extend 60-input-id.rules to allow for bus/vid/pid/name matches Same approach as used in 70-mouse.rules, allow for a name-based match optionally combined with bus/vid/pid (which the existing modalias rule would already allow us anyway). Note that ID_BUS isn't assigned until after this rule has run so we need to use the id/bustype attribute directly. Related to https://github.com/systemd/systemd/issues/36677 2025-10-09 10:55:16 +10:00			`# id-input:<bus>:v<vid>p<pid>:name:<name>:*`
			`KERNELS=="input*", ATTRS{id/bustype}=="0003", \`
			`IMPORT{builtin}="hwdb 'id-input:usb:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'", \`
			`GOTO="id_input_end"`
			`KERNELS=="input*", ATTRS{id/bustype}=="0005", \`
			`IMPORT{builtin}="hwdb 'id-input:bluetooth:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'", \`
			`GOTO="id_input_end"`
			`KERNELS=="input*", ATTRS{id/bustype}=="0018", \`
			`IMPORT{builtin}="hwdb 'id-input:i2c:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'", \`
			`GOTO="id_input_end"`

rules: move input_id rule to a separate file This places the input_id call after the evdev hwdb calls. With this the hwdb fixups in evdev can affect the device capabilities assigned in input_id. Remove the ID_INPUT_KEY dependency in atkbd rule because it is now not assigned at this point. 2017-06-12 13:43:05 +02:00			`LABEL="id_input_end"`