Documentation/ABI/stable/sysfs-driver-w1_ds28e04

Source file repositories/reference/linux-study-clean/Documentation/ABI/stable/sysfs-driver-w1_ds28e04

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/stable/sysfs-driver-w1_ds28e04
Extension: [no extension]
Size: 656 bytes
Lines: 16
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/w1/devices/.../pio
Date:		May 2012
Contact:	Markus Franke <franm@hrz.tu-chemnitz.de>
Description:	read/write the contents of the two PIO's of the DS28E04-100
		see Documentation/w1/slaves/w1_ds28e04.rst for detailed information
Users:		any user space application which wants to communicate with DS28E04-100



What:		/sys/bus/w1/devices/.../eeprom
Date:		May 2012
Contact:	Markus Franke <franm@hrz.tu-chemnitz.de>
Description:	read/write the contents of the EEPROM memory of the DS28E04-100
		see Documentation/w1/slaves/w1_ds28e04.rst for detailed information
Users:		any user space application which wants to communicate with DS28E04-100

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.