diff options
| author | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2026-08-03 11:46:26 -0700 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.com> | 2026-08-14 14:46:20 +0200 |
| commit | be978be17296d8b304c252933bcb13324173c2d2 (patch) | |
| tree | 79ddb00d5e2056c7eca7a7c9a3ee959854d2692b /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 99e9bd11684af923bd34b7116ec22ea256f3f55e (diff) | |
HID: core: automatically initialize generic FF if no other FF is present
Some HID drivers initialize their own force-feedback support within
their .input_configured() callback. In such cases, we should skip
the generic PID force-feedback initialization to avoid conflicts and
redundant setup.
Add hid_has_ff_input() helper and use it to check for existing FF
capabilities before calling hdev->ff_init().
Since we now have a dynamic way to detect if force-feedback is needed,
the HID_CONNECT_FF flag is redundant for conflict resolution and can
be ignored in the core initialization logic. Generic PID support will
now be attempted by default for any claimed input device that doesn't
already have FF capabilities.
Assisted-by: Gemini:gemini-3.1-pro
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
