Documentation/ABI/testing/sysfs-driver-input-exc3000

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

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-driver-input-exc3000
Extension: [no extension]
Size: 774 bytes
Lines: 27
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/xxx/fw_version
Date:		Aug 2020
Contact:	linux-input@vger.kernel.org
Description:    Reports the firmware version provided by the touchscreen, for example "00_T6" on a EXC80H60

		Access: Read

		Valid values: Represented as string

What:		/sys/bus/i2c/devices/xxx/model
Date:		Aug 2020
Contact:	linux-input@vger.kernel.org
Description:    Reports the model identification provided by the touchscreen, for example "Orion_1320" on a EXC80H60

		Access: Read

		Valid values: Represented as string

What:		/sys/bus/i2c/devices/xxx/type
Date:		Jan 2021
Contact:	linux-input@vger.kernel.org
Description:	Reports the type identification provided by the touchscreen, for example "PCAP82H80 Series"

		Access: Read

		Valid values: Represented as string

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.