input_inject_event(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 input_inject_event(9) 🎀

okay bestie, welcome to the Kernel API Manual entry for input_inject_event — yes the title is literally the function name, we're keeping it real 💅

✨ NAME ✨

input_inject_event — send input event from input handler 🦋

🌸 SYNOPSIS 🌸

void input_inject_event (struct input_handle *handle , unsigned int type
, unsigned int code , int value );
no cap, that's the whole signature — void, so don't go looking for a return value, it's not coming 😭

💖 ARGUMENTS 💖

  • handle — the input handle you're sending the event through, like your little delivery girl 🎀
  • type — type of the event, the category bestie, the vibe check of the event
  • code — event code, the specific one, iykyk
  • value — value of the event, the actual deets 💅

👑 DESCRIPTION 👑

okay so here's the tea ☕ — input_inject_event is similar to input_event, bestie. like, they're sisters, same energy, but there's one iconic difference:

it will ignore the event if the device is "grabbed" and the handle injecting the event is not the one that owns the device. periodt 💀

so like, if somebody else grabbed the device and you're not them? your event is literally not making it through. not yours. none for you. <em>the audacity, I know</em> 🙈 but that's the whole point — the grab owner gets the monopoly, no jumping the queue 🧚

🔥 SEE ALSO 🔥

the whole friend group, fr fr — Kernel file ./drivers/input/input.c plus:

and that's the page, bestie 💜 this whole thing lives in ./drivers/input and it's dated October 2026, still input_inject_event(9) to the very end — slay, ate, no crumbs 🌈✨🫶

📦 where this page comes from