Documentation/ABI/testing/sysfs-driver-w1_ds28e17

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

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-driver-w1_ds28e17
Extension: [no extension]
Size: 817 bytes
Lines: 25
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/19-<id>/speed
Date:		Sep 2017
KernelVersion:	4.14
Contact:	Jan Kandziora <jjj@gmx.de>
Description:	When written, this file sets the I2C speed on the connected
		DS28E17 chip. When read, it reads the current setting from
		the DS28E17 chip.

		Valid values: 100, 400, 900 [kBaud].

		Default 100, can be set by w1_ds28e17.speed= module parameter.
Users:		w1_ds28e17 driver

What:		/sys/bus/w1/devices/19-<id>/stretch
Date:		Sep 2017
KernelVersion:	4.14
Contact:	Jan Kandziora <jjj@gmx.de>
Description:	When written, this file sets the multiplier used to calculate
		the busy timeout for I2C operations on the connected DS28E17
		chip. When read, returns the current setting.
		Valid values: 1 to 9.

		Default 1, can be set by w1_ds28e17.stretch= module parameter.
Users:		w1_ds28e17 driver

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.