iio_device_r...ger_consumer(9)

💅 iio_device_register_trigger_consumer(9) — the Kernel API Manual, bestie edition 🎀

okay so this is a page straight out of the Kernel API Manual, and it's a short one — a true little snack ✨ It's about iio_device_register_trigger_consumer, which is giving "wire up an iio_dev so it can consume triggers" energy. Let's get into it 🦋

🌸 NAME 🌸

iio_device_register_trigger_consumer — literally just sets up an iio_dev to use triggers. that's the whole vibe. no cap 💅

✨ SYNOPSIS ✨

int iio_device_register_trigger_consumer (struct iio_dev *indio_dev );

it returns an int, it takes exactly one arg, and it's gonna be the main character of this whole page 👑

🫶 ARGUMENTS 🫶

• indio_dev — the iio_dev that's associated with the device which will be consuming the trigger. like, this is the device, the one with the appetite, the one doing the consuming 🍓 so yeah, hand it over and it's gonna be the trigger consumer, periodt.

🔥 SEE ALSO 🔥

• Kernel file: ./drivers/iio/iio_core_trigger.h — go read the header, bestie, it's right there 📄
• iio_device_unregister_trigger_consumer(9) — the undoing one, the cleanup crew 🧹
• iio_device_unregister_trigger_consumer(9) — and yes, it's listed again. twice. two separate entries, same name. not me pointing it out, but like… it's literally right there in the original 🙈 iykyk. keeping it because facts are facts 💯

🌈 a little sign-off 🌈

and that's the whole page, gorgeous 💖 this one lives over in ./drivers/iio, stamped October 2026, and it answers to the name iio_device_r...ger_consumer(9) — yes, with the lil' ellipsis, she's mysterious like that ⭐ mwah, slay, go register some triggers 👑💅