Documentation/ABI/testing/sysfs-bus-coresight-devices-trbe

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-bus-coresight-devices-trbe

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-bus-coresight-devices-trbe
Extension: [no extension]
Size: 781 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/bus/coresight/devices/trbe<cpu>/align
Date:		March 2021
KernelVersion:	5.13
Contact:	Anshuman Khandual <anshuman.khandual@arm.com>
Description:	(Read) Shows the TRBE write pointer alignment. This value
		is fetched from the TRBIDR register.

What:		/sys/bus/coresight/devices/trbe<cpu>/flag
Date:		March 2021
KernelVersion:	5.13
Contact:	Anshuman Khandual <anshuman.khandual@arm.com>
Description:	(Read) Shows if TRBE updates in the memory are with access
		and dirty flag updates as well. This value is fetched from
		the TRBIDR register.

What:           /sys/bus/coresight/devices/trbe<cpu>/label
Date:           Aug 2025
KernelVersion   6.18
Contact:        Mao Jinlong <quic_jinlmao@quicinc.com>
Description:    (Read) Show hardware context information of 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.