Documentation/ABI/testing/sysfs-driver-xilinx-tmr-manager

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-driver-xilinx-tmr-manager

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-driver-xilinx-tmr-manager
Extension: [no extension]
Size: 760 bytes
Lines: 17
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/devices/platform/amba_pl/<dev>/errcnt
Date:          Nov 2022
Contact:       appana.durga.kedareswara.rao@amd.com
Description:   This control file provides the fault detection count.
               This file cannot be written.
               Example:
               # cat /sys/devices/platform/amba_pl/44a10000.tmr_manager/errcnt
               1

What:          /sys/devices/platform/amba_pl/<dev>/dis_block_break
Date:          Nov 2022
Contact:       appana.durga.kedareswara.rao@amd.com
Description:   Write any value to it, This control file enables the break signal.
               This file is write only.
               Example:
               # echo <any value> > /sys/devices/platform/amba_pl/44a10000.tmr_manager/dis_block_break

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.