input_mt_rep...finger_count(9)

📦 version 7.3.1, in nixpkgs unstable

hey bestie 💖 welcome to the Kernel API Manual page for input_mt_rep...finger_count(9) — yep, the manual name is serving abbreviated-ellipsis realness, but the function we're actually hyping is input_mt_report_finger_count, and she is the main character here. 🎀

🌸 NAME 🌸

input_mt_report_finger_count — report contact count. That's the whole assignment, and she ate. ✨

✨ SYNOPSIS ✨

void input_mt_report_finger_count (struct input_dev *dev , int count );

ngl the signature is giving void, with dev and count showing up exactly like that. no extra drama, periodt. 💅

🫶 ARGUMENTS 🫶

  • dev — input device with allocated MT slots. hand over the device that already has its MT slots allocated, bestie. 🌈
  • count — the number of contacts. literally the contact count, fr fr. 🍓

💖 DESCRIPTION 💖

Okay so this function reports the contact count via these iconic button events: BTN_TOOL_FINGER, BTN_TOOL_DOUBLETAP, BTN_TOOL_TRIPLETAP, and BTN_TOOL_QUADTAP. periodt. 🔥

Here's the safety-vibe note: the input core ensures only the KEY events already setup for this device will produce output. so the output stays selective, iykyk. 💀

🌟 SEE ALSO 🌟

The Kernel file ./drivers/input/input-mt.c is right there, plus all these related besties:

k bye bestie 🫶 — this page's source is ./drivers/input, it's dated October 2026, and input_mt_rep...finger_count(9) is signing off with a little sparkle. slay. 💅✨

📦 where this page comes from