STRUCT TB_NVM_VENDOR_OPS(9)

💅 struct tb_nvm_vendor_ops(9) — like, the Kernel API Manual bestie ✨

okay so real talk, this is the <pink>Kernel API Manual</pink> entry for struct tb_nvm_vendor_ops, and it's genuinely one of those little structs that's giving main character energy in the Thunderbolt NVM world 🦋

---

🌸 NAME 🌸

struct tb_nvm_vendor_ops — Vendor specific NVM operations 💖

Like, it's literally the struct where a vendor plugs in its own custom NVM behaviour. no cap.

---

✨ SYNOPSIS ✨

struct tb_nvm_vendor_ops {
    int (*read_version)(struct tb_nvm *nvm);
    int (*validate)(struct tb_nvm *nvm);
    int (*write_headers)(struct tb_nvm *nvm);
 };

three function pointers, three vibes, one struct 🎀 that's it that's the whole thing.

---

🫶 Members 🫶

• read_version — reads out the NVM version from the flash 🔥 like, it goes and fetches the version for you. iconic behaviour honestly.
• validate — validates the NVM image before update. it's optional, so no pressure bestie 💅
• write_headers — writes the headers before the rest of the image. also optional 🌸 order matters here, headers first, then the rest, iykyk.

lowkey reminder: validate and write_headers are both marked optional, so a vendor doesn't have to fill them in. read_version has no such note. 🙈

---

👑 SEE ALSO 👑

kernel file ./drivers/thunderbolt/nvm.c, plus the whole friend group:

• struct tb_nvm_vendor(9)
• tb_nvm_alloc(9)
• tb_nvm_read_version(9)
• tb_nvm_validate(9)
• tb_nvm_write_headers(9)
• tb_nvm_add_active(9)
• tb_nvm_write_buf(9)
• tb_nvm_add_non_active(9)
• tb_nvm_free(9)
• tb_nvm_read_data(9)
• tb_nvm_write_data(9)

fr fr go read them, they all ate 💀⭐

---

aaaand that's the page! 🧚 sign-off time: this lil beauty lives in ./drivers/thunderbolt, it's dated October 2026, and yes the title is still struct tb_nvm_vendor_ops(9) because we don't do rebrands here 🍓💜