touch_overlay_map(9)

💅 touch_overlay_map(9) — bestie's Kernel API Manual era ✨

Okay so bestie, this is touch_overlay_map(9) from the Kernel API Manual, and it's lowkey iconic. We're mapping overlay objects, setting key capabilities when buttons exist, and keeping every single detail intact. No cap. 🫶

🎀 NAME 🎀

touch_overlay_map — the way that this function maps overlay objects from the device tree is giving main character energy, and if buttons are defined it sets key capabilities accordingly. That's the name-section vibe. Slay. ✨

🌸 SYNOPSIS 🌸

       int touch_overlay_map (struct list_head *list , struct input_dev *input
       );

The signature said what it said, and we're keeping it exactly like that. 💅

🔥 ARGUMENTS 🔥

• list — pointer to the list that will hold the segments. Yes bestie, it's a struct list_head *, and it's literally there to hold the segments. 💖
• input — pointer to the already allocated input_dev. Already allocated, no cap. ✨

🦋 DESCRIPTION 🦋

Here's the tea: this bad boy returns 0 on success and error number otherwise. That's the vibe check: 0 means success, and anything else means error number. Periodt. 💅

If buttons are defined, key capabilities are set accordingly. That's the whole plot, and it ate. 🔥

🌈 SEE ALSO 🌈

• Kernel file ./drivers/input/touch-overlay.c — the source file, main character energy. 🎀
• touch_overlay_get_touchscreen_abs(9) — bestie reference, go look. 🫶
• touch_overlay_mapped_touchscreen(9) — another iconic reference. 🌸
• touch_overlay_sync_frame(9) — sync frame realness, fr fr. 💜
• touch_overlay_process_contact(9) — process contact, slay. ⭐

Okay bestie, that's the whole manual page: every argument, return value, buttons note, and SEE ALSO reference is here. No skipped details. 💖

Signing off from the ./drivers/input source/version corner, dated October 2026, with touch_overlay_map(9) energy forever. Byeee! 💅✨🎀