sparse_keym...rom_scancode(9)
β¨ NAME β¨
sparse_keymap_entry_from_scancode β bestie, this is the one that does the sparse keymap lookup π
(it lives in the Kernel API Manual, iykyk π)
πΈ SYNOPSIS πΈ
struct key_entry * sparse_keymap_entry_from_scancode (struct input_dev
*dev , unsigned int code );
π¦ ARGUMENTS π¦
devβ the input device that's out here using a sparse keymap π«Άcodeβ the scan code, literally just the scan code
π DESCRIPTION π
okay so picture this: this function is the one you call when you wanna do a struct key_entry lookup on an input device that's running a sparse keymap. that's it, that's the whole vibe β¨
like, it's giving "find me the key entry for this thing" energy, no cap π₯
π SEE ALSO π
- Kernel file
./drivers/input/sparse-keymap.c sparse_keymap_entry_from_keycode(9)sparse_keymap_setup(9)sparse_keymap_report_entry(9)sparse_keymap_report_event(9)
go read the whole friend group, they're all iconic π
fr fr that's the whole page, and it slayed πβ¨
signing off from ./drivers/input, October 2026, mwah ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms