input_get_keycode(9)

💖 input_get_keycode(9) 💖

okay so this is the Kernel API Manual page for input_get_keycode(9), and it's literally about grabbing the keycode that's currently mapped to a given scancode. bestie, it's short and cute, so let's get into it 💅

---

🌸 NAME 🌸

input_get_keycode — retrieve keycode currently mapped to a given scancode.

---

✨ SYNOPSIS ✨

int input_get_keycode (struct input_dev *dev , struct input_keymap_entry
       *ke );

---

🫶 ARGUMENTS 🫶

• dev — the input device whose keymap is being queried. like, this is the device we're asking about 🔍
• ke — keymap entry. the little keymap entry thingy 💖

---

💅 DESCRIPTION 💅

okay so the manual says this function should be called by anyone interested in retrieving the current keymap. presently, evdev handlers use it. that's the whole vibe — it's the "hey what's the current keymap?" function, and evdev handlers are the current users. no cap ✨

---

🌈 SEE ALSO 🌈

you'll also wanna check these out, bestie:

• Kernel file ./drivers/input/input.c
• input_event(9)
• input_inject_event(9)
• input_alloc_absinfo(9)
• input_copy_abs(9)
• input_grab_device(9)
• input_release_device(9)
• input_open_device(9)
• input_close_device(9)
• input_scancode_to_scalar(9)
• input_default_setkeycode(9)
• input_set_keycode(9)
• input_reset_device(9)
• input_allocate_device(9)
• devm_input_allocate_device(9)
• input_free_device(9)
• input_set_timestamp(9)
• input_get_timestamp(9)
• input_set_capability(9)
• input_enable_softrepeat(9)
• input_register_device(9)
• input_unregister_device(9)
• input_register_handler(9)
• input_unregister_handler(9)
• input_handler_for_each_handle(9)
• input_register_handle(9)
• input_unregister_handle(9)
• input_get_new_minor(9)
• input_free_minor(9)

---

xoxo, this page is input_get_keycode(9) — source/version ./drivers/input, dated October 2026 💅✨