auxiliary_de...ysfs_irq_add(9)

✨ auxiliary_de...ysfs_irq_add(9) ✨

okay bestie, this one comes straight from the Kernel API Manual 💖. The main character is auxiliary_device_sysfs_irq_add, and her whole job is adding a sysfs entry for the IRQ you hand her. slay.

🌸 NAME 🌸

auxiliary_device_sysfs_irq_add — add a sysfs entry for the given IRQ. periodt.

🎀 SYNOPSIS 🎀

int auxiliary_device_sysfs_irq_add (struct auxiliary_device *auxdev ,
       int irq );

🦋 ARGUMENTS 🦋

• auxdev — the auxiliary bus device where we're adding the sysfs entry. that's her 💅
• irq — the associated interrupt number. yep, the IRQ in question ✨

💅 DESCRIPTION 💅

okay so here's the tea: call this function after the auxiliary device has successfully received the IRQ. no cap.

The driver is responsible for adding a unique IRQ for the auxiliary device. that part is literally on the driver 🫶

The driver can invoke this function from multiple thread contexts safely for unique IRQs of auxiliary devices. so multithreaded besties can do their thing — as long as the IRQs are unique 🌈

🚨 but the driver must not invoke this API multiple times if the IRQ was already added previously. that is not the vibe. please do not do that, bestie 😭

🌈 RETURN 🌈

zero on success, or an error code on failure. that's the return vibe check 💀

👑 SEE ALSO 👑

• Kernel file ./drivers/base/auxiliary_sysfs.c
• auxiliary_device_sysfs_irq_remove(9)

---

mwah 💋 this page lives under ./drivers/base, dated October 2026, and it's all about auxiliary_de...ysfs_irq_add(9). bye bestie, go add those sysfs IRQ entries responsibly 🎀✨