include/linux/platform_data/si5351.h

File Facts

System

Linux kernel

Corpus path

include/linux/platform_data/si5351.h

Extension

.h

Size

3733 bytes

Lines

118

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source 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 or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• struct si5351_clkout_config
• struct si5351_platform_data
• enum si5351_pll_src
• enum si5351_multisynth_src
• enum si5351_clkout_src
• enum si5351_drive_strength
• enum si5351_disable_state

Annotated Snippet

struct si5351_clkout_config {
	enum si5351_multisynth_src multisynth_src;
	enum si5351_clkout_src clkout_src;
	enum si5351_drive_strength drive;
	enum si5351_disable_state disable_state;
	bool pll_master;
	bool pll_reset;
	unsigned long rate;
};

/**
 * struct si5351_platform_data - Platform data for the Si5351 clock driver
 * @clk_xtal: xtal input clock
 * @clk_clkin: clkin input clock
 * @pll_src: array of pll source clock setting
 * @pll_reset: array indicating if plls should be reset after setting the rate
 * @clkout: array of clkout configuration
 */
struct si5351_platform_data {
	enum si5351_pll_src pll_src[2];
	bool pll_reset[2];
	struct si5351_clkout_config clkout[8];
};

#endif

Annotation

• Detected declarations: `struct si5351_clkout_config`, `struct si5351_platform_data`, `enum si5351_pll_src`, `enum si5351_multisynth_src`, `enum si5351_clkout_src`, `enum si5351_drive_strength`, `enum si5351_disable_state`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source 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.