Due to how evdev work, this is a "glitch" when a program read analog value from '/dev/input/input0', this can be easily seen via 'evtest'.
Fuzz and deadzone parameters are simply ignored.
This problem does not exist when reading from '/dev/input/js0' via jstest.
Edit: This is normal, evdev and joystick are 2 different things.
The workaround for deadzone could is to constrain the analog values in the driver.
For fuzz, there is nothing to do.
Nota:
/include/uapi/linux/input.h:66 : struct input_absinfo
@flat: values that are within this value will be discarded by joydev interface and reported as 0 instead.
/driver/input/joydev.c:950
- [Pushed to Github] Workaround to apply analog deadzone to evdev, addition of ADC_Deadzone() function, no additional modification in config file.
Fuzz and deadzone parameters are simply ignored.
This problem does not exist when reading from '/dev/input/js0' via jstest.
Edit: This is normal, evdev and joystick are 2 different things.
The workaround for deadzone could is to constrain the analog values in the driver.
For fuzz, there is nothing to do.
Nota:
/include/uapi/linux/input.h:66 : struct input_absinfo
@flat: values that are within this value will be discarded by joydev interface and reported as 0 instead.
/driver/input/joydev.c:950
- [Pushed to Github] Workaround to apply analog deadzone to evdev, addition of ADC_Deadzone() function, no additional modification in config file.