Documentation/ABI/testing/sysfs-bus-intel_th-output-devices

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-bus-intel_th-output-devices

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-bus-intel_th-output-devices
Extension: [no extension]
Size: 681 bytes
Lines: 16
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/intel_th/devices/<intel_th_id>-<device><id>/active
Date:		June 2015
KernelVersion:	4.3
Contact:	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Description:	(RW) Writes of 1 or 0 enable or disable trace output to this
		output device. Reads return current status. Requires that the
		correstponding output port driver be loaded.

What:		/sys/bus/intel_th/devices/<intel_th_id>-msc<msc-id>/port
Date:		June 2015
KernelVersion:	4.3
Contact:	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Description:	(RO) Port number, corresponding to this output device on the
		switch (GTH) or "unassigned" if the corresponding output
		port driver is not loaded.

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.