drivers/clk/qcom/clk-hfpll.h
Source file repositories/reference/linux-study-clean/drivers/clk/qcom/clk-hfpll.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/clk/qcom/clk-hfpll.h- Extension
.h- Size
- 754 bytes
- Lines
- 46
- Domain
- Driver Families
- Bucket
- drivers/clk
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/clk-provider.hlinux/spinlock.hclk-regmap.h
Detected Declarations
struct hfpll_datastruct clk_hfpll
Annotated Snippet
struct hfpll_data {
u32 mode_reg;
u32 l_reg;
u32 m_reg;
u32 n_reg;
u32 user_reg;
u32 droop_reg;
u32 config_reg;
u32 status_reg;
u8 lock_bit;
u32 l_val;
u32 droop_val;
u32 config_val;
u32 user_val;
u32 user_vco_mask;
unsigned long low_vco_max_rate;
unsigned long min_rate;
unsigned long max_rate;
};
struct clk_hfpll {
struct hfpll_data const *d;
int init_done;
struct clk_regmap clkr;
spinlock_t lock;
};
#define to_clk_hfpll(_hw) \
container_of(to_clk_regmap(_hw), struct clk_hfpll, clkr)
extern const struct clk_ops clk_ops_hfpll;
#endif
Annotation
- Immediate include surface: `linux/clk-provider.h`, `linux/spinlock.h`, `clk-regmap.h`.
- Detected declarations: `struct hfpll_data`, `struct clk_hfpll`.
- Atlas domain: Driver Families / drivers/clk.
- 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.