We did a board based on the Novena core. It had a rotary coder connected via GPIO pins. The device tree file had the following definition:
compatible = "rotary-encoder";
gpios = <&gpio2 21 GPIO_ACTIVE_HIGH>, <&gpio1 02 GPIO_ACTIVE_HIGH>;
linux,axis = <REL_WHEEL>;
Upon initialization, the kernel would create an evdev device present under /dev/input/. This device has only a mouse wheel, and no other axes. In order to get the device to actually send events to applications, the following xorg.conf.d file was created:
Identifier "Rotary encoder"
So it works once you apply that config? In that case we need to fix the udev builtin to label devices for us. Or just bite the bullet and enable evdev for all event* devices, but that's not a good idea.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-input-evdev/issues/4.