Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x
Extension: [no extension]
Size: 1007 bytes
Lines: 24
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/i2c/.../idle_state
Date:		January 2019
KernelVersion:	5.2
Contact:	Robert Shearman <robert.shearman@att.com>
Description:
		Value that exists only for mux devices that can be
		written to control the behaviour of the multiplexer on
		idle. Possible values:

		===========  ===============================================
		-2	     disconnect on idle, i.e. deselect the last used
			     channel, which is useful when there is a device
			     with an address that conflicts with another
			     device on another mux on the same parent bus.
		-1	     leave the mux as-is, which is the most optimal
			     setting in terms of I2C operations and is the
			     default mode.
		0..<nchans>  set the mux to a predetermined channel,
			     which is useful if there is one channel that is
			     used almost always, and you want to reduce the
			     latency for normal operations after rare
			     transactions on other channels
		===========  ===============================================

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.