input_default_setkeycode(9)

📦 version 7.3.1, in nixpkgs unstable

💅 input_default_setkeycode(9) — like, the default setkeycode method, bestie

okay so this is a page from the Kernel API Manual (section 9, kernel dev girlies rise up 🫶) and it's all about input_default_setkeycode. it's giving "the standard-issue implementation" and honestly? iconic. ✨

✨ SYNOPSIS ✨

int input_default_setkeycode (struct input_dev *dev , const struct
       input_keymap_entry *ke , unsigned int *old_keycode );

three args, one int back, no cap. 🎀

🌸 ARGUMENTS 🌸

  • dev — the input device whose keymap is being updated, like, right now, in real time. main character device energy 👑
  • ke — the new keymap entry. this is the new hotness about to drop. 🔥
  • old_keycode — a pointer to the spot where the old keycode should get stored. yes, you gotta keep the ex. it goes here. 💅

🦋 DESCRIPTION 🦋

so this function is the default implementation of the input_dev.setkeycode method. meaning: if a driver can't be bothered to write its own version, this one shows up and handles it. lowkey the friend who always drives. 🚗

but also — and this is the part that ate — it's exported too, so drivers can call it and extend it if they want. so it's not just the fallback, it's the fallback and the building block. versatile queen. 👑

⚠️ okay so important: the function must be called with input_dev.event_lock held. like, that's not a suggestion, bestie. lock first, then call. fr fr. 🔒

⭐ RETURN ⭐

0 on success, or a negative error code on failure. that's it, that's the vibe check. 💀

🎀 SEE ALSO 🎀

the kernel file ./drivers/input/input.c (iykyk 🌈) plus, like, the entire extended universe of input functions. buckle up:

literally the whole friend group 💖 go read them all, i'll wait.

and that's the page!! shipped from ./drivers/input, stamped October 2026, and titled input_default_setkeycode(9) in the Kernel API Manual. slay, go hold that event_lock, and stan responsibly. 💜🦋✨

📦 where this page comes from