auxiliary_d...s_irq_remove(9)

💅 auxiliary_device_sysfs_irq_remove(9) — from the Kernel API Manual, bestie

Okay so bestie, we're in the Kernel API Manual today and the star of the show is auxiliary_device_sysfs_irq_remove. Yes it's a long name. Yes it ate. Let's get into it ✨

---

🎀 NAME 🎀

auxiliary_device_sysfs_irq_remove — literally removes a sysfs entry for the given IRQ. That's the whole vibe. No cap. 🦋

---

✨ SYNOPSIS ✨

void auxiliary_device_sysfs_irq_remove (struct auxiliary_device *auxdev
, int irq );

It returns void, meaning it gives you nothing back and expects nothing from you. Lowkey iconic of it. 💅

---

🫶 ARGUMENTS 🫶

• auxdev — the auxiliary bus device to add the sysfs entry. (Yes, that's what the page says — "add". We're just reporting the lore here, don't come for me 🙈)
• irq — the IRQ to remove. Simple. Clean. Slay. ⭐

---

🔥 DESCRIPTION 🔥

So here's the tea: this function should be called to remove an IRQ sysfs entry. Like, that's its whole job. 🎀

The driver must invoke this API when the IRQ is released by the device. Not "maybe", not "whenever you feel like it" — must. It's giving main character energy with rules, fr fr. 👑

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/base/auxiliary_sysfs.c
• auxiliary_device_sysfs_irq_add(9) — the add counterpart, the sibling, the duo we stan 🧚

---

Bestie's gentle reminder: this page lives in ./drivers/base and it's dated October 2026 — so screenshot it, cite it, love it, and go remove those sysfs entries responsibly. Periodt. 💖🌸💜