sparse_keymap_report_event(9)

📦 version 7.3.1, in nixpkgs unstable

💅 sparse_keymap_report_event(9) — the Kernel API Manual glow-up ✨

okay so bestie, welcome to the sparse_keymap_report_event page from the Kernel API Manual, and honestly? she's a baddie. let's get into it 🎀

🌸 NAME 🌸

sparse_keymap_report_event — report the event that corresponds to a given scancode. that's it, that's the whole vibe 🦋

✨ SYNOPSIS ✨

bool sparse_keymap_report_event (struct input_dev *dev , unsigned int
       code , unsigned int value , bool autorelease );

look at that signature. she's serving bool, she's taking four args, she's iconic 👑

🫶 ARGUMENTS 🫶

  • dev — the input device that's using the sparse keymap. like, the main character here 💖
  • code — the scan code. yes queen, the actual key thing 🔥
  • value — the value that should be reported. lowkey important: this one is ignored by KE_SW entries, so don't come for her if she doesn't read it 🙈
  • autorelease — signals whether a release event should be emitted for KE_KEY entries right after reporting the press event. for real fr fr: it's ignored by all other entries, so it only matters for KE_KEY, no cap 💅

💜 DESCRIPTION 💜

so what does she even do? this function is used to perform a lookup in an input device that's using a sparse keymap, and then report the corresponding event. that's the whole gig ✨

and the return value? true if the lookup was successful, false otherwise. she's honest like that 💀

🌈 SEE ALSO 🌈

the whole friend group, together again 🫶

and that's the page!! mwah 💋 this little baddie lives in ./drivers/input, and the version of this manual page is dated October 2026 — so yeah, she's fresh, she's current, she ate and left no crumbs 👑⭐🍓

📦 where this page comes from