input_mt_re...er_emulation(9)

📦 version 7.3.1, in nixpkgs unstable

💅 input_mt_re...er_emulation(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — yes the title is literally truncated like that on the page, input_mt_re...er_emulation(9), and no I will not be explaining why, the kernel just does that sometimes 🫶. This is the whole thing about common pointer emulation, and it's lowkey iconic. Let's get into it.

✨ NAME ✨

input_mt_report_pointer_emulation — common pointer emulation 🎀

🌸 SYNOPSIS 🌸

void input_mt_report_pointer_emulation (struct input_dev *dev , bool
use_count );

like, that's the whole call signature, no cap 💖

🦋 ARGUMENTS 🦋

  • dev — the input device that's got MT slots allocated already, bestie. If it doesn't have them, this is not the vibe 😭
  • use_count — when this is true, you're reporting the number of active contacts as the finger count. fr fr, that's it 🫶

⭐ DESCRIPTION ⭐

So what does it actually do? It performs legacy pointer emulation via BTN_TOUCH, ABS_X, ABS_Y and ABS_PRESSURE 👑 — yes, the old-school squad, still showing up to the function, main character energy tbh.

Touchpad finger count gets emulated if use_count is true 💅 periodt.

And here's the part you cannot skip, bestie, write it on your hand: the input core ensures only the KEY and ABS axes already setup for this device will produce output 🌈. So like. If it wasn't set up, it's not coming out. That's the vibe check and everything passes it ✨.

💜 SEE ALSO 💜

Kernel file ./drivers/input/input-mt.c — the source file, go read it, it's giving lore 📖

the whole friend group honestly, all of them slay 🧚‍♀️💖

ok that's the whole page, no gatekeeping here 🙈

and finally, the cute sign-off: this lil masterpiece lives in ./drivers/input, it's dated October 2026 🌸, and it's filed under input_mt_re...er_emulation(9) — yeah, same truncated name, it's a whole aesthetic at this point 💀✨ byeee 🦋💜

📦 where this page comes from