AttrEventCodeEnable and AttrEventCodeDisable cannot be stacked
See !815 (comment 1638230) for the original analysis.
Where a device has AttrEventCodeEnable
and AttrEventCodeDisable
applied to it (via two separate quirks), the Disable
always takes precedence. This is due to the implementation in evdev_pre_configure_model_quirks()
which runs through the enabled codes first, then the disabled codes. In the case of !815 (closed), a generic quirk had disable, a specific quirk used enable but it still ended up getting disabled.
The same behaviour applies to AttrInputPropEnable
and AttrInputPropDisable
.