STRUCT FW_UPLOAD_OPS(9)

💅 struct fw_upload_ops(9) — like, the Kernel API Manual, but make it make sense 🎀

okay so bestie, welcome to struct fw_upload_ops — this is the Kernel API Manual entry for the struct you're gonna meet the second you touch firmware upload. it's the little bundle of device-specific operations that make firmware upload actually work ✨

---

✨ NAME ✨

struct fw_upload_ops — device specific operations to support firmware upload 🫶

like… the ops your device has to bring to the party so the kernel can push firmware onto it. no ops, no upload. periodt.

---

🌸 SYNOPSIS 🌸

struct fw_upload_ops {
    enum fw_upload_err (*prepare)(struct fw_upload *fw_upload, const u8 *data, u32 size);
    enum fw_upload_err (*write)(struct fw_upload *fw_upload, const u8 *data, u32 offset, u32 size, u32 *written);
    enum fw_upload_err (*poll_complete)(struct fw_upload *fw_upload);
    void (*cancel)(struct fw_upload *fw_upload);
    void (*cleanup)(struct fw_upload *fw_upload);
 };

five function pointers, that's the whole vibe check. copy it exactly, don't get creative with the signatures, i'm begging 😭

---

🦋 Members 🦋

💖 the required ones (no skipping, fr fr)

• prepare — Required: Prepare secure update. it's literally the opener, the "hey bestie let's get this started" of the whole flow 🔥
• write — Required: The write op receives the remaining size to be written and must return the actual size written or a negative error code. The write op will be called repeatedly until all data is written.

okay so this one's a loop situation — it gets called over and over until everything is written. and the way that it has to return the actual size written OR a negative error code… return the right numbers or the whole thing falls apart, ngl 💀

• poll_complete — Required: Check for the completion of the HW authentication/programming process. you're basically asking "are we there yet" at the hardware level, iconic 🌈
• cancel — Required: Request cancellation of update. This op is called from the context of a different kernel thread, so race conditions need to be considered.

⚠️ not me warning you about race conditions ⚠️ — this gets called from a different kernel thread, so yeah, concurrency brain on. consider your race conditions, bestie, for real 🧚

🎀 the optional one

• cleanup — Optional: Complements the prepare function and is called at the completion of the update, on success or failure, if the prepare function succeeded.

the fine print tho: it runs on success or failure — but only if prepare succeeded. so if prepare flopped, cleanup doesn't get the invite 🙈 💅

---

⭐ SEE ALSO ⭐

• Kernel file ./include/linux/firmware.h
• enum fw_upload_err(9)

go read those next, iykyk ✨

---

and that's the whole page, bestie — sending you off with love from ./include/linux, October 2026 edition of struct fw_upload_ops(9). slay, go upload some firmware responsibly 👑💜🦋