fcp_bus_reset(9)

✨ fcp_bus_reset — bestie, the bus just reset ✨

okay so real talk, this little page lives in the Kernel API Manual, and it's short but it's important, so pay attention 🫶

---

🌸 NAME 🌸

fcp_bus_reset — the function that slides into the target handler's DMs to be like "hey girl, a bus reset happened" 💅

---

🎀 SYNOPSIS 🎀

void fcp_bus_reset (struct fw_unit *unit );

that's the whole signature. no cap, she's tiny but she's doing the lord's work ✨

---

🦋 ARGUMENTS 🦋

• unit — the unit that might be used by fcp_avc_transaction. that's it, that's the whole argument. she's the one who might be involved, so she gets the heads up 💖

---

🔥 DESCRIPTION 🔥

okay so listen up because this is the part that actually matters 👑

You must call this function from the driver's .update handler. like, not "should", not "maybe", must. it's giving non-negotiable 😤

Its whole job? Tell the FCP transaction handler that a bus reset has happened. That's the vibe check. The handler hears the news and then, because it's a good little handler, any pending FCP transactions are retried 🔁✨

so the flow is: bus resets → you call fcp_bus_reset from .update → handler finds out → pending transactions get retried. slay, everyone's informed, nothing gets left on read 💌

not me emphasizing this again but fr fr: it's gotta be the driver's .update handler. that's the assignment. 🎯

---

👑 SEE ALSO 👑

• Kernel file ./sound/firewire/fcp.c
• fcp_avc_transaction(9)

go read those too, iykyk 📚💜

---

and that's the whole page bestie, you ate that 🍓 stay iconic, keep your .update handlers honest, and remember: transactions that get retried are transactions that get to live another day 🌈⭐

with love from ./sound/firewire, October 2026 — mwah 💋