iio_device_u...ger_consumer(9)

💅 iio_device_u...ger_consumer(9) 💅

okay so bestie, welcome to the Kernel API Manual — this one's a tiny little function page from the IIO subsystem, and honestly? It's short, it's sweet, and it's the clean-up arc of the trigger-consumer story. Let's get into it. 🎀

---

✨ NAME ✨

iio_device_unregister_trigger_consumer — it literally does the reverse of the registration process. that's it. that's the whole vibe. undo what got done. 🫶

---

🌸 SYNOPSIS 🌸

void iio_device_unregister_trigger_consumer(struct iio_dev *indio_dev);

no return value, no drama — it's a void function, so it's giving "I handle my business and I don't report back." 💅 ✨

---

🦋 ARGUMENTS 🦋

• indio_dev — the iio_dev associated with the device that consumed the trigger. fr fr, that's the one you pass in — the device that was doing the consuming. 🍓

---

👑 SEE ALSO 👑

• the kernel file ./drivers/iio/iio_core_trigger.h — go look, it's right there in the tree 💜
• iio_device_register_trigger_consumer(9)
• iio_device_register_trigger_consumer(9)

yes bestie, that reference is listed twice in the original. not a typo on my end — I'm keeping it exactly as it is. the register function simply ate and left no crumbs, so it gets two shoutouts. 🔥👑

---

🌈 sign-off 🌈

and that's the whole page! short king behavior honestly. this lil gem lives under the source ./drivers/iio and it's dated October 2026 — so yeah, mark your calendars, the trigger consumer registration lore continues. 😭✨ mwah, study hard, and remember: register it, then unregister it. balance. 🧚💖