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

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

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480
Extension: [no extension]
Size: 772 bytes
Lines: 28
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/devices/.../device
Date:		February 2011
Contact:	Minkyu Kang <mk7.kang@samsung.com>
Description:
		show what device is attached

		=======  ======================
		NONE     no device
		USB      USB device is attached
		UART     UART is attached
		CHARGER  Charger is attached
		JIG      JIG is attached
		=======  ======================

What:		/sys/bus/i2c/devices/.../switch
Date:		February 2011
Contact:	Minkyu Kang <mk7.kang@samsung.com>
Description:
		show or set the state of manual switch

		=======  ==============================
		VAUDIO   switch to VAUDIO path
		UART     switch to UART path
		AUDIO    switch to AUDIO path
		DHOST    switch to DHOST path
		AUTO     switch automatically by device
		=======  ==============================

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.