init_ohci139...or_busresets(9)

💖 init_ohci1394_wait_for_busresets(9) 💖

okay so this little icon is from the Kernel API Manual, and it's literally all about waiting until bus resets are done. bestie, let's get into it 🫶

---

✨ NAME ✨

init_ohci1394_wait_for_busresets — wait until bus resets are completed 💅

---

🌸 SYNOPSIS 🌸

void init_ohci1394_wait_for_busresets (struct ohci *ohci );

---

🎀 ARGUMENTS 🎀

• ohci — Pointer to the OHCI-1394 controller structure ✨

---

💅 DESCRIPTION 💅

okay so here's the tea, bestie: OHCI1394 initialization itself causes an IEEE1394 bus reset. Any device going on- or offline? also an IEEE1394 bus reset. Any cable issue? yup, IEEE1394 bus reset. it's giving bus reset everywhere 😭

The OHCI1394 spec specifies that physical DMA is disabled on each bus reset, and it has to be enabled after each bus reset when needed. so yeah, that's the rule 📜

We resort to polling here because on early boot, we have no interrupts. no cap — that's literally why this function is doing the waiting game ⏳💖

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/firewire/init_ohci1394_dma.c 🎀
• init_ohci1394_enable_physical_dma(9) ✨
• init_ohci1394_reset_and_init_dma(9) 💫
• init_ohci1394_controller(9) 🌟
• init_ohci1394_dma_on_all_controllers(9) 💖
• setup_ohci1394_dma(9) 🫶

---

xoxo, signed sealed and delivered by the ./drivers/firewire girlies — October 2026 💌🎀