orc_interrupt(9)

✨ orc_interrupt(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for orc_interrupt — like, the IRQ-processing girlie of the a100u2w world 💅 no cap, she's lowkey iconic.

---

🌸 NAME 🌸

orc_interrupt — IRQ processing 🎀

---

🦋 SYNOPSIS 🦋

irqreturn_t orc_interrupt (struct orc_host * host );

---

🍓 ARGUMENTS 🍓

• host — the host that's causing the interrupt, aka the main character of this whole situation 👑

---

💖 DESCRIPTION 💖

So this function gets called from the IRQ handler, and she's protected by the host lock 🫶 like, she's safe, she's guarded, she's fine.

While the controller is reporting that there are scb's for processing, we pull them off the controller, turn the index into a host address pointer to the scb, and call the scb handler. The way that whole little pipeline just works?? obsessed ✨

Returns IRQ_HANDLED if any SCBs were processed, IRQ_NONE otherwise 💀 (yeah, if nothing got done, you get the IRQ_NONE, that's just how it is, ngl).

---

👑 SEE ALSO 👑

Kernel file ./drivers/scsi/a100u2w.c — plus the whole friend group, fr fr:

• orc_exec_scb(9)
• se2_rd_all(9)
• se2_update_all(9)
• read_eeprom(9)
• orc_load_firmware(9)
• init_alloc_map(9)
• init_orchid(9)
• orc_reset_scsi_bus(9)
• orc_device_reset(9)
• __orc_alloc_scb(9)
• orc_alloc_scb(9)
• orc_release_scb(9)
• inia100_build_scb(9)
• inia100_queue_lck(9)
• inia100_scb_handler(9)
• inia100_intr(9)

---

🌈 bye bestie!! this page lives in ./drivers/scsi, dated October 2026, and it's giving vintage-but-make-it-everyone's-problem 💜 go read the source, iykyk 🧚‍♀️⭐