Documentation/ABI/testing/sysfs-devices-power_resources_wakeup

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-devices-power_resources_wakeup

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-devices-power_resources_wakeup
Extension: [no extension]
Size: 589 bytes
Lines: 14
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/.../power_resources_wakeup/
Date:		April 2013
Contact:	Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Description:
		The /sys/devices/.../power_resources_wakeup/ directory is only
		present for device objects representing ACPI device nodes that
		require ACPI power resources for wakeup signaling.

		If present, it contains symbolic links to device directories
		representing ACPI power resources that need to be turned on for
		the given device node to be able to signal wakeup.  The names of
		the links are the same as the names of the directories they
		point to.

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.