input_set_capability(9)

📦 version 7.3.1, in nixpkgs unstable

💅 input_set_capability — kernel API manual, but make it make sense

okay so bestie, welcome to the <pink>input_set_capability(9)</pink> page from the Kernel API Manual — yes that's the manual name, we're being official today 🎀. This is the glow-up function that tells the whole input subsystem "hey, this device can do this thing," so buckle up 🦋

✨ NAME ✨

input_set_capability — mark device as capable of a certain event. literally just declaring what your device is able to do, no cap 💅

🌸 SYNOPSIS 🌸

void input_set_capability (struct input_dev *dev , unsigned int type ,
unsigned int code );

that's the whole vibe: three args, void return, in we go ✨

🎀 ARGUMENTS 🎀

  • dev — the device that is capable of emitting or accepting event. like, the actual input device in question, the main character 👑
  • type — type of the event (EV_KEY, EV_REL, etc...). the category of thing we're talking about here 🗂️
  • code — event code. the specific one inside that category, iykyk 🔥

💖 DESCRIPTION 💖

so here's the tea ☕ — in addition to setting up corresponding bit in appropriate capability bitmap, the function also adjusts dev->evbit. two things, one call, we love an efficient queen 🫶

like. it does the bitmap thing AND it pokes dev->evbit for you. no need to go do it yourself, bestie, it's handled ✨💅

👑 SEE ALSO 👑

Kernel file ./drivers/input/input.c — and then the whole squad, fr fr, here's every single one 🦋:

and that's the page!! 🩷 this lil beauty lives in the <purple>./drivers/input</purple> source and it's dated October 2026 — so go forth, set those capabilities, and slay 💅✨🌟

📦 where this page comes from