Documentation/ABI/testing/sysfs-nvmem-cells

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-nvmem-cells

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-nvmem-cells
Extension: [no extension]
Size: 870 bytes
Lines: 22
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: Documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

What:		/sys/bus/nvmem/devices/.../cells/<cell-name>
Date:		May 2023
KernelVersion:	6.5
Contact:	Miquel Raynal <miquel.raynal@bootlin.com>
Description:
		The "cells" folder contains one file per cell exposed by the
		NVMEM device. The name of the file is: "<name>@<byte>,<bit>",
		with <name> being the cell name and <where> its location in
		the NVMEM device, in hexadecimal bytes and bits (without the
		'0x' prefix, to mimic device tree node names). The length of
		the file is the size of the cell (when known). The content of
		the file is the binary content of the cell (may sometimes be
		ASCII, likely without trailing character).
		Note: This file is only present if CONFIG_NVMEM_SYSFS
		is enabled.

		Example::

		  hexdump -C /sys/bus/nvmem/devices/1-00563/cells/product-name@d,0
		  00000000  54 4e 34 38 4d 2d 50 2d  44 4e         |TN48M-P-DN|
		  0000000a

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.