Documentation/ABI/testing/sysfs-driver-jz4780-efuse

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-driver-jz4780-efuse

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-driver-jz4780-efuse
Extension: [no extension]
Size: 692 bytes
Lines: 21
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/devices/*/<our-device>/nvmem
Date:		December 2017
Contact:	PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Description:	read-only access to the efuse on the Ingenic JZ4780 SoC
		The SoC has a one time programmable 8K efuse that is
		split into segments. The driver supports read only.
		The segments are:

		===== ======== =================
		0x000   64 bit Random Number
		0x008  128 bit Ingenic Chip ID
		0x018  128 bit Customer ID
		0x028 3520 bit Reserved
		0x1E0    8 bit Protect Segment
		0x1E1 2296 bit HDMI Key
		0x300 2048 bit Security boot key
		===== ======== =================

Users:		any user space application which wants to read the Chip
		and Customer ID

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.