Bug 219189 - EV_FF_STATUS does not go anywhere after submitted by a driver
Summary: EV_FF_STATUS does not go anywhere after submitted by a driver
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-21 17:57 UTC by Katharine Chui
Modified: 2024-08-21 17:57 UTC (History)
0 users

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Katharine Chui 2024-08-21 17:57:58 UTC
Be it a from a native input driver or from uinput, EV_FF_STATUS cannot get through to evdev https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/input/input.c?h=v6.10#n241 .

Wine seems to use it, if the udev backend is used in winebus, https://gitlab.winehq.org/wine/wine/-/blob/6e15604c48acd63dd8095a4ce2fd011cb3be96db/dlls/winebus.sys/bus_udev.c#L709, it would be used to provide driver updated effect status for IDirectInputEffect::GetEffectStatus.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/input/ff.rst?h=v6.10#n237 says that it is incomplete, but didn't state why it was incomplete.

So, what is the plan for EV_FF_STATUS? In it's current state it doesn't do anything even with the iforce driver. Should it just get INPUT_PASS_TO_HANDLERS so that other drivers and application can start using it? Should it get deprecated since it doesn't quite do anything?

Note You need to log in before you can comment on or make changes to this bug.