Documentation/ABI/stable/sysfs-acpi-pmprofile

Source file repositories/reference/linux-study-clean/Documentation/ABI/stable/sysfs-acpi-pmprofile

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/stable/sysfs-acpi-pmprofile
Extension: [no extension]
Size: 841 bytes
Lines: 29
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/acpi/pm_profile
Date:		03-Nov-2011
KernelVersion:	v3.2
Contact:	linux-acpi@vger.kernel.org
Description:	The ACPI pm_profile sysfs interface exposes the preferred
		power management (and performance) profile of the platform
		as provided in the ACPI FADT Preferred_PM_Profile field.

		The integer value is directly passed as retrieved from the FADT.

Values:	        For the possible values refer to the Preferred_PM_Profile field
		definition in Table 5.9 "FADT Format", Section 5.2.9 "Fixed ACPI
		Description Table (FADT)" of the ACPI specification.

		As of ACPI 6.5, the following values are defined:

		== =================
		0  Unspecified
		1  Desktop
		2  Mobile
		3  Workstation
		4  Enterprise Server
		5  SOHO Server
		6  Appliance PC
		7  Performance Server
		8  Tablet
		>8 Reserved
		== =================

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.