iio_trigger...e_own_device(9)

✨ NAME ✨

hiii bestie 💖 welcome to the iio_trigger...e_own_device(9) page in the Kernel API Manual. This is all about iio_trigger_validate_own_device — check if a trigger and IIO device belong to the same device. It's giving "are y'all actually together or not" energy. 🎀

🌸 SYNOPSIS 🌸

int iio_trigger_validate_own_device (struct iio_trigger *trig , struct
iio_dev *indio_dev );

🦋 ARGUMENTS 🦋

• trig — the IIO trigger to check 👀
• indio_dev — the IIO device to check, periodt.

💅 DESCRIPTION 💅

So basically this function can be used as the validate_device callback for triggers that can only be attached to their own device. That's the whole assignment, no cap. ✨

🔥 RETURN 🔥

• 0 — both the trigger and the IIO device belong to the same device, slay 💖
• -EINVAL — otherwise, aka not the same device, and it said what it said 💀

🌈 SEE ALSO 🌈

Kernel file ./drivers/iio/industrialio-trigger.c has the receipts, and you should also check out:

• name_show(9)
• iio_trigger_poll(9)
• iio_trigger_poll_nested(9)
• current_trigger_show(9)
• current_trigger_store(9)
• __iio_trigger_alloc(9)
• __devm_iio_trigger_alloc(9)
• devm_iio_trigger_register(9)
• iio_validate_own_trigger(9)

mwah 💋 — signed off from ./drivers/iio, dated October 2026, on the iio_trigger...e_own_device(9) page. bye bestie, go check those triggers! 🫶