drivers/clk/sprd/common.h
Source file repositories/reference/linux-study-clean/drivers/clk/sprd/common.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/clk/sprd/common.h- Extension
.h- Size
- 913 bytes
- Lines
- 39
- 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/of_platform.hlinux/regmap.h
Detected Declarations
struct device_nodestruct sprd_clk_commonstruct sprd_clk_descfunction hw_to_sprd_clk_common
Annotated Snippet
struct sprd_clk_common {
struct regmap *regmap;
u32 reg;
struct clk_hw hw;
};
struct sprd_clk_desc {
struct sprd_clk_common **clk_clks;
unsigned long num_clk_clks;
struct clk_hw_onecell_data *hw_clks;
};
static inline struct sprd_clk_common *
hw_to_sprd_clk_common(const struct clk_hw *hw)
{
return container_of(hw, struct sprd_clk_common, hw);
}
int sprd_clk_regmap_init(struct platform_device *pdev,
const struct sprd_clk_desc *desc);
int sprd_clk_probe(struct device *dev, struct clk_hw_onecell_data *clkhw);
#endif /* _SPRD_CLK_COMMON_H_ */
Annotation
- Immediate include surface: `linux/clk-provider.h`, `linux/of_platform.h`, `linux/regmap.h`.
- Detected declarations: `struct device_node`, `struct sprd_clk_common`, `struct sprd_clk_desc`, `function hw_to_sprd_clk_common`.
- 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.