nvmem_cell_...iable_le_u64(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

NAME πŸ’–

okay so bestie, welcome to nvmem_cell_...iable_le_u64(9) from the Kernel API Manual β€” the function is nvmem_cell_read_variable_le_u64, and it’s literally here to read up to 64-bits of data as a little endian number. slay. ✨


SYNOPSIS πŸŽ€

int nvmem_cell_read_variable_le_u64 (struct device *dev , const char
*cell_id , u64 *val );

ARGUMENTS 🫢

  • dev β€” Device that requests the nvmem cell. it’s the one asking for the read, main character energy fr.
  • cell_id β€” Name of nvmem cell to read. yep, the name is the whole vibe check here.
  • val β€” pointer to output value. that’s where the answer lands, bestie.

RETURN πŸ’…

0 on success or negative errno. no cap β€” success is 0, and anything else is a negative errno situation. 😭


SEE ALSO 🌈

Kernel file ./drivers/nvmem/core.c is the source, and here’s the whole SEE ALSO friend group β€” every single one, periodt:

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_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_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 πŸ’‹ this iconic little page comes from ./drivers/nvmem, dated October 2026, and it’s serving Kernel API Manual realness β€” bye bestie! πŸ¦‹

πŸ“¦ where this page comes from