odoo/odoo#195576
Created by fw-bot
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/template: Contact runbot team on discord for help.
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:17.0-16.0-hw_drivers-fix-foot-pedals-yaso-f2VS-fw
- head
- ba36ce679d4ef831ad5b7b131fedd05a2a104d2f
- merged
- 8 months ago by POS IoT, Quentin Lejeune (qle)
| odoo/odoo | |
|---|---|
| 16.0 | #195306 |
| 17.0 | #195576 |
| saas-17.2 | #195652 |
| saas-17.4 | #195671 |
| 18.0 | #195687 |
| saas-18.1 | #195713 |
| saas-18.2 | |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| master | #195728 |
[FW][FIX] hw_drivers: fix foot pedals
Currently foot pedals often don't send their input to Odoo This is due to the fact that the foot pedals are detected as 1 usb device which is associated with 3 separate event files for its 3 different fonctionalities (a foot switch can work as a keyboard, a mouse and a joystick)
Our current code only detects input from one of these 3 event files (the last one in the list) while the input is actually only sent to the keyboard event file.
Since "evdev" and "usb core" libraries don't allow us to determine which evdev device is the right one this PR allows listening to all of the event files associated to a usb device to read input from all of them.
This PR also adds some comment to simplify the understanding of the input detection and event files structure on Linux.
Note: on IoT Box images > 25.01 the user "odoo" which runs Odoo service needs to be in the group "input" to be able to correctly detect evdev devices and have access to their event files.
Related PR:
195307
Forward-Port-Of: #195306