devm_iio_trigger_register(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_iio_trigger_register(9) 💅

okay bestie, welcome to the Kernel API Manual — this one's short and sweet, no cap. it's the resource-managed glow-up of iio_trigger_register(), and honestly? iconic behaviour. ✨

🌸 NAME 🌸

devm_iio_trigger_register — it's iio_trigger_register(), but make it resource-managed. the devm version. the one that cleans up after itself. 🧹

🎀 SYNOPSIS 🎀

int devm_iio_trigger_register (struct device *dev , struct iio_trigger
*trig_info );

two args, one int coming back at you. that's the whole vibe check. 🦋

✨ ARGUMENTS ✨

  • dev — the struct device * this trigger was allocated for. like, whose trigger is this? this one's. 🫶
  • trig_info — the struct iio_trigger * you actually wanna register. the trigger in question. the main character. 👑

💖 DESCRIPTION 💖

so here's the tea: this is the managed iio_trigger_register. the IIO trigger you register through this function gets automatically unregistered on driver detach — no manual cleanup era, we love a self-sufficient queen. 🌈

internally it straight up calls iio_trigger_register (fr fr, that's where the real work happens). so if you want the full lore, go read that function — this page is literally just the devm wrapper telling you it exists. 😭

🔥 RETURN 🔥

  • 0 on success — slay, you did it 💅
  • a negative error number on failure — not slay, go check the errno 💀

🦋 SEE ALSO 🦋

Kernel file ./drivers/iio/industrialio-trigger.c — plus the whole friend group:

lowkey reminder bestie: the auto-unregister only happens because it's devm-flavoured. that's the entire point. don't come crying if you used the non-managed one and forgot to clean up 🙈

⭐ okay that's the page!! brought to you by the <pink>./drivers/iio</pink> girlies, October 2026 edition, devm_iio_trigger_register(9) forever and always 🎀💜🍓

📦 where this page comes from