STRUCT TELEM_DEVICE_DATA(9)

💖 struct telem_device_data(9) 💖

okay bestie, welcome to the Kernel API Manual ✨ — this is the page for struct telem_device_data, and yes it's from that kernel API manual thing, we're doing this, buckle up 🎀

---

✨ NAME ✨

struct telem_device_data — literally the data for a Wilco EC device that queries telemetry 🦋 (yes, that's the whole name, it does exactly what it says on the tin)

---

🌸 SYNOPSIS 🌸

struct telem_device_data {
    struct device dev;
    struct cdev cdev;
    struct wilco_ec_device *ec;
    atomic_t available;
 };

that's the struct, bestie, copy it exactly, no cap 💅

---

👑 Members 👑

• dev — the struct device that's associated with the cdev 🫶
• cdev — the char dev that userspace reads and polls from 📖 (userspace said "give me data", and this is the door it knocks on)
• ec — the Wilco EC that we will be communicating with using the mailbox interface ✉️ (mailbox interface. very demure, very mindful)
• available — a boolean of if the device can be opened 🔓 (is the vibe check passing? this tells you)

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/platform/chrome/wilco_ec/telemetry.c
• struct wilco_ec_telem_request(9)
• check_telem_request(9)
• struct telem_session_data(9)
• telem_open(9)
• telem_device_free(9)
• telem_device_probe(9)

go read those too, iykyk 👀 the whole little friend group is right there 💜

---

lowkey important: everything above is exactly as documented — the struct fields, the member descriptions, and every single SEE ALSO reference. no invented lore, periodt 💀

---

and that's the page!! 🌸 source file is ./drivers/platform/chrome/wilc... (the footer truncates it like that, we respect the ellipsis 🥲) and it's dated October 2026, from the Kernel API Manual, filed under struct telem_device_data(9) ⭐ k bye bestie, slay your telemetry queries 💖🧚‍♀️🎀