irq_set_chip..._name_locked(9)

💅 irq_set_chip..._name_locked(9) — from the Kernel API Manual, bestie ✨

okay so this is irq_set_chip_handler_name_locked, straight out of the Linux Kernel API Manual, and honestly? she's a little power move. let me put you on 🫶

---

✨ NAME ✨

irq_set_chip_handler_name_locked — literally "set chip, handler and name from a locked region" 💖 that's the whole job, no cap.

---

🌸 SYNOPSIS 🌸

void irq_set_chip_handler_name_locked (struct irq_data *data , const
       struct irq_chip *chip , irq_flow_handler_t handler , const char *name );

like, yes, she returns void. she gives nothing back because she's already given everything. icon behavior 💅

---

🎀 ARGUMENTS 🎀

• data — pointer to the irq_data structure for which the chip is set. this is the main character of the whole operation, fr.
• chip — pointer to the new irq chip. the glow-up in question ✨
• handler — flow control handler function for this interrupt. she handles the flow, iykyk.
• name — name of the interrupt. yes bestie she gets a name, we love a labeled queen 👑

---

🦋 DESCRIPTION 🦋

so what she actually does: she replaces the irq chip at the proper hierarchy level in data, and sets the handler and name in the associated irq descriptor. that's three things at once. multitasking icon 💀🔥

⚠️ okay this part is serious though: must be called with irq_desc locked and valid parameters. not optional, not a suggestion. locked region or bust. no cap. 🙈

---

🌈 SEE ALSO 🌈

• the kernel file ./include/linux/irqdesc.h
• struct irqstat(9)
• struct irq_redirect(9)
• struct irq_desc(9)
• irq_set_handler_locked(9) — her sister, also slaying ✨

---

and that's the whole vibe check, bestie 🍓 this came to you from ./include/linux, dated October 2026, filed under irq_set_chip..._name_locked(9) — mwah, go forth and lock your irq_desc 💜🧚‍♀️