nvmem_device_get(9)

💖 NAME 💖

okay so bestie, this is nvmem_device_get(9) from the Kernel API Manual, and its whole job is: Get nvmem device from a given id ✨. That's the vibe. It's giving "hand me the nvmem device that matches this id" energy, no cap 💅.

✨ SYNOPSIS ✨

struct nvmem_device * nvmem_device_get (struct device *dev , const char
       *dev_name );

🎀 ARGUMENTS 🎀

• dev — the device that uses the nvmem device 🫶. Like, this is the device doing the using, okay?
• dev_name — the name of the requested nvmem device 🌸. Literally the name you're asking for, bestie.

🌸 RETURN 🌸

Vibe check: it returns ERR_PTR on error 😭, or a valid pointer to a struct nvmem_device on success 👑. So either sad error-pointer energy or the actual nvmem device pointer, periodt.

🦋 SEE ALSO 🦋

bestie, there is a whole friend group of related pages and the kernel file itself. Peep them all:

• Kernel file: ./drivers/nvmem/core.c 📁
• nvmem_add_one_cell(9)
• nvmem_add_cells(9)
• nvmem_register_notifier(9)
• nvmem_unregister_notifier(9)
• nvmem_register(9)
• nvmem_unregister(9)
• devm_nvmem_register(9)
• of_nvmem_device_get(9)
• nvmem_device_find(9)
• devm_nvmem_device_put(9)
• nvmem_device_put(9)
• devm_nvmem_device_get(9)
• of_nvmem_cell_get(9)
• nvmem_cell_get(9)
• devm_nvmem_cell_get(9)
• devm_nvmem_cell_put(9)
• nvmem_cell_put(9)
• nvmem_cell_read(9)
• nvmem_cell_write(9)
• nvmem_cell_read_u8(9)
• nvmem_cell_read_u16(9)
• nvmem_cell_read_u32(9)
• nvmem_cell_read_u64(9)
• nvmem_cell_read_variable_le_u32(9)
• nvmem_cell_read_variable_le_u64(9)
• nvmem_device_cell_read(9)
• nvmem_device_cell_write(9)
• nvmem_device_read(9)
• nvmem_device_write(9)
• nvmem_add_cell_lookups(9)
• nvmem_del_cell_lookups(9)
• nvmem_dev_name(9)
• nvmem_dev_size(9)

mwah 💋 — source/version ./drivers/nvmem, date October 2026, and this page is nvmem_device_get(9) 🫶 byeee 💅