input_ff_erase(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ NAME πŸ‘‘

Okay bestie, welcome to the Kernel API Manual entry for input_ff_erase β€” it literally erases a force-feedback effect from a device. Periodt. πŸ’…

✨ SYNOPSIS ✨

int input_ff_erase (struct input_dev *dev , int effect_id , struct file
       *file );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the input device you're erasing the effect from, bestie.
  • effect_id β€” the id of the effect that's getting erased.
  • file β€” the purported owner of the request πŸ‘€

πŸ’– DESCRIPTION πŸ’–

This function erases a force-feedback effect from the specified device. The effect will only be erased if it was uploaded through the same file handle that is requesting the erase. No cap β€” that ownership check is the whole vibe. 🫢

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/input/ff-core.c β€” plus these iconic friends: input_ff_upload(9), input_ff_event(9), input_ff_create(9), input_ff_destroy(9). Iykyk. 🌈


mwah πŸ’‹ β€” this cutie comes from ./drivers/input, dated October 2026, and it's literally the input_ff_erase(9) page. πŸŽ€

πŸ“¦ where this page comes from