Documentation/ABI/testing/sysfs-bus-iio-thermocouple

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-bus-iio-thermocouple

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-bus-iio-thermocouple
Extension: [no extension]
Size: 683 bytes
Lines: 19
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/iio/devices/iio:deviceX/fault_ovuv
KernelVersion:	5.1
Contact:	linux-iio@vger.kernel.org
Description:
		Overvoltage or Undervoltage Input Fault. The internal circuitry
		is protected from excessive voltages applied to the thermocouple
		cables. The device can also detect if such a condition occurs.

		Reading returns '1' if input voltage is negative or greater
		than VDD, otherwise '0'.

What:		/sys/bus/iio/devices/iio:deviceX/fault_oc
KernelVersion:	5.1
Contact:	linux-iio@vger.kernel.org
Description:
		Open-circuit fault. The detection of open-circuit faults,
		such as those caused by broken thermocouple wires.
		Reading returns '1' if fault, '0' otherwise.

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.