Documentation/ABI/testing/debugfs-iio-backend

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/debugfs-iio-backend

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/debugfs-iio-backend
Extension: [no extension]
Size: 557 bytes
Lines: 21
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/kernel/debug/iio/iio:deviceX/backendY/name
KernelVersion:	6.11
Contact:	linux-iio@vger.kernel.org
Description:
		Name of Backend Y connected to device X.

What:		/sys/kernel/debug/iio/iio:deviceX/backendY/direct_reg_access
KernelVersion:	6.11
Contact:	linux-iio@vger.kernel.org
Description:
		Directly access the registers of backend Y. Typical usage is:

		Reading address 0x50
		echo 0x50 > direct_reg_access
		cat direct_reg_access

		Writing address 0x50
		echo 0x50 0x3 > direct_reg_access
		//readback address 0x50
		cat direct_reg_access

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.