tb_nvm_add_active(9)

💖 tb_nvm_add_active(9) 💖

okay so bestie, welcome to the Kernel API Manual — this one's a (9) section page, which means it's kernel-internals territory. it's literally about plugging a shiny new active NVMem device into your Thunderbolt NVM and honestly? iconic. ✨

---

🦋 NAME 🦋

tb_nvm_add_active — Adds active NVMem device to NVM

like, the whole personality of this function is right there in the name, no cap 💅

---

🌸 SYNOPSIS 🌸

int tb_nvm_add_active (struct tb_nvm *nvm , nvmem_reg_read_t reg_read );

that's the whole vibe check right there 🫶

---

🎀 ARGUMENTS 🎀

• nvm — the NVM structure. your main character struct, the whole reason we're here 💖
• reg_read — Pointer to the function to read the NVM (passed directly to the NVMem device). it gets handed straight over to the NVMem device, so it's living its best life on the other side 😭

---

✨ DESCRIPTION ✨

Registers new active NVmem device for nvm. 🎉

so here's the tea: reg_read is called directly from NVMem, which means it is fully on its own out there — it must handle possible concurrent access if needed. no hand-holding, no safety net, it's giving independent woman energy 👑

and just so you know, the first parameter passed to reg_read is the nvm structure. cute, right? that's the little detail you don't wanna forget 🙈

---

🔥 RETURN 🔥

• 0 on success 🥳
• negative errno otherwise 💀

---

💜 SEE ALSO 💜

Kernel file ./drivers/thunderbolt/nvm.c and the rest of the squad:

• struct tb_nvm_vendor_ops(9)
• 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_write_buf(9)
• tb_nvm_add_non_active(9) — yes, the non-active sibling, we love both equally 🌈
• tb_nvm_free(9)
• tb_nvm_read_data(9)
• tb_nvm_write_data(9)

go read them all, i'll wait 💅

---

and that's the page bestie!! this one came out of ./drivers/thunderbolt back in October 2026 — go forth and register those active NVMem devices responsibly 🧚‍♀️⭐💖