Documentation/ABI/testing/sysfs-firmware-opal-psr

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-firmware-opal-psr

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-firmware-opal-psr
Extension: [no extension]
Size: 718 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/firmware/opal/psr
Date:		August 2017
Contact:	Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
Description:	Power-Shift-Ratio directory for Powernv P9 servers

		Power-Shift-Ratio allows to provide hints the firmware
		to shift/throttle power between different entities in
		the system. Each attribute in this directory indicates
		a settable PSR.

What:		/sys/firmware/opal/psr/cpu_to_gpu_X
Date:		August 2017
Contact:	Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
Description:	PSR sysfs attributes for Powernv P9 servers

		Power-Shift-Ratio between CPU and GPU for a given chip
		with chip-id X. This file gives the ratio (0-100)
		which is used by OCC for power-capping.

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.