STRUCT TB_NVM_VENDOR(9)

💖 struct tb_nvm_vendor(9) 💖

Hiii bestie 🫶 welcome to the Kernel API Manual, where today’s main character is literally struct tb_nvm_vendor(9). It’s giving vendor-to-&struct tb_nvm_vendor_ops mapping, and we are obsessed. ✨

🌸 NAME 🌸

struct tb_nvm_vendor — Vendor to &struct tb_nvm_vendor_ops mapping 💅

🦋 SYNOPSIS 🦋

Here’s the whole struct, no cap:

struct tb_nvm_vendor {
    u16 vendor;
    const struct tb_nvm_vendor_ops *vops;
 };

🎀 Members 🎀

• vendor — Vendor ID, periodt. 🆔
• vops — Vendor specific NVM operations, slay. 🛠️

🔥 Description 🔥

Okay so this struct maps a vendor ID to NVM vendor operations. If there is no mapping, then NVM firmware upgrade is disabled for the device. That’s the vibe check: no mapping, no upgrade. 💀

👑 SEE ALSO 👑

Kernel file ./drivers/thunderbolt/nvm.c has all the lore, plus these besties:

• struct tb_nvm_vendor_ops(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)

Later, bestie 🫶 this page’s source/version is ./drivers/thunderbolt, dated October 2026, and it’s still struct tb_nvm_vendor(9) — iykyk. Stay slay, and don’t forget the mapping. ✨💖🎀