touch_overla..._touchscreen(9)

✨ touch_overla..._touchscreen(9) ✨

okay so bestie, welcome to the Kernel API Manual — yes it's a real manual, yes the title is literally truncated with ... in it, and no we are not going to fix it, that's just how it shipped 💅

---

🎀 NAME 🎀

touch_overlay_mapped_touchscreen — the little function that checks if a touchscreen area is mapped. that's it. that's the whole job. icon behavior honestly 🫶

---

🌸 SYNOPSIS 🌸

bool touch_overlay_mapped_touchscreen (struct list_head *list );

like yes she returns a bool, yes the spacing is exactly that, do not come for me about the space before the ) 😭

---

🦋 ARGUMENTS 🦋

• list — pointer to the list that holds the segments. that's the whole vibe. it's a struct list_head * and it's carrying the segments, periodt ✨

---

💖 DESCRIPTION 💖

Returns true if a touchscreen area is mapped, or false otherwise. that's literally it bestie — one job, zero drama, no cap 🔥

so if you're sitting there wondering "is this touchscreen area mapped or not", you call her, you hand her the list that holds the segments, and she tells you true or false. main character energy fr fr 👑

---

👑 SEE ALSO 👑

• Kernel file ./drivers/input/touch-overlay.c (yes, that's the whole source file, go read it, iykyk 📖)
• touch_overlay_map(9)
• touch_overlay_get_touchscreen_abs(9)
• touch_overlay_sync_frame(9)
• touch_overlay_process_contact(9)

go read the whole friend group, they're all iconic in their own way 🧚

---

lowkey a reminder that this page lives in the kernel API docs under section 9, so when you see the (9) everywhere that's why — not me being random, that's just the section 🌈

---

and that's the page!! mwah 💋 — brought to you by ./drivers/input, dated October 2026, starring touch_overla..._touchscreen(9) one more time for the people in the back 🍓✨