touchscreen_...e_properties(9)

📦 version 7.3.1, in nixpkgs unstable

💅 touchscreen_parse_properties(9) — Kernel API Manual 🎀

okay so bestie, we're in the Kernel API Manual today and this page is literally about parsing touchscreen properties. yes, like the touchscreen. the one you're probably scrolling this on. iconic behaviour fr fr.

✨ NAME ✨

touchscreen_parse_properties — parse common touchscreen properties 🫶

🌸 SYNOPSIS 🌸

void touchscreen_parse_properties (struct input_dev *input , bool
multitouch , struct touchscreen_properties *prop );

like, look at her. three args, returns nothing, does her job. no notes. 👑

🦋 ARGUMENTS 🦋

  • input — the input device that should be parsed 💖 this is the main character of the whole operation.
  • multitouch — a bool that specifies whether the parsed properties should be applied to single-touch axes or multi-touch axes. so it's giving "pick your lane" energy 🌈
  • prop — pointer to a struct touchscreen_properties into which to store axis swap and invert info, for use with touchscreen_report_x_y — or NULL. yeah, NULL is a valid vibe here, no cap 🙈

⭐ DESCRIPTION ⭐

This function parses common properties for touchscreens and sets up the input device accordingly. periodt. 💅

and the sweet part? the function keeps previously set up default values if no value is specified. so like, if you don't say anything, she's not gonna change your settings behind your back — she just leaves them. lowkey respectful tbh 🧚

👑 SEE ALSO 👑

Kernel file ./drivers/input/touchscreen.c — plus these two icons:

go read them, iykyk 📚✨

ngl bestie, always double-check that prop situation before you pass it in — the page says NULL is allowed, and we believe the docs, but that's the only note i'm giving you 💀 (no extra tips invented here, just repeating what the page says fr fr)

mwah 💋 that's the page!! it's coming at you from source <purple>./drivers/input</purple> and it's dated October 2026 — so yes, we're reading from the future, and we ate. 🔥🫶🍓

📦 where this page comes from