tb_nvm_add_non_active(9)

🌸 NAME 🌸

hey bestie, welcome to the Kernel API Manual page for tb_nvm_add_non_active(9) 💖. The name says it all: tb_nvm_add_non_active — adds a non-active NVMem device to NVM. Slay.

✨ SYNOPSIS ✨

the exact signature, no cap:

int tb_nvm_add_non_active (struct tb_nvm *nvm , nvmem_reg_write_t
reg_write );

🎀 ARGUMENTS 🎀

• nvm — NVM structure.
• reg_write — pointer to the function to write the NVM (passed directly to the NVMem device).

🦋 DESCRIPTION 🦋

okay so here's the vibe: it registers a new non-active NVmem device for nvm. ✨

Important bestie note: reg_write is called directly from NVMem, so it must handle possible concurrent access if needed. The first parameter passed to reg_write is the nvm structure. The size of the NVMem device is set to NVM_MAX_SIZE. 💅

💖 RETURN 💖

0 on success, negative errno otherwise. That's the whole return vibe, fr fr.

🌈 SEE ALSO 🌈

go check these out, iykyk:

• Kernel file ./drivers/thunderbolt/nvm.c
• 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_add_active(9)
• tb_nvm_write_buf(9)
• tb_nvm_free(9)
• tb_nvm_read_data(9)
• tb_nvm_write_data(9)

mwah 💋 — source/version: ./drivers/thunderbolt, date: October 2026, and page: tb_nvm_add_non_active(9) 🫶