include/linux/pm_clock.h

File Facts

System

Linux kernel

Corpus path

include/linux/pm_clock.h

Extension

.h

Size

2437 bytes

Lines

99

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: operation-table or driver-model contract

Status

pattern implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/device.h
• linux/notifier.h

Detected Declarations

• struct pm_clk_notifier_block
• struct clk
• function pm_clk_no_clocks
• function pm_clk_no_clocks
• function pm_clk_init
• function pm_clk_destroy
• function pm_clk_add_clk
• function of_pm_clk_add_clks
• function pm_clk_remove_clk
• function pm_clk_add_notifier

Annotated Snippet

extern void pm_clk_add_notifier(const struct bus_type *bus,
					struct pm_clk_notifier_block *clknb);
#else
static inline void pm_clk_add_notifier(const struct bus_type *bus,
					struct pm_clk_notifier_block *clknb)
{
}
#endif

#endif

Annotation

• Immediate include surface: `linux/device.h`, `linux/notifier.h`.
• Detected declarations: `struct pm_clk_notifier_block`, `struct clk`, `function pm_clk_no_clocks`, `function pm_clk_no_clocks`, `function pm_clk_init`, `function pm_clk_destroy`, `function pm_clk_add_clk`, `function of_pm_clk_add_clks`, `function pm_clk_remove_clk`, `function pm_clk_add_notifier`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: pattern implementation candidate.

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.