drivers/clk/actions/owl-common.c
Source file repositories/reference/linux-study-clean/drivers/clk/actions/owl-common.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/clk/actions/owl-common.c- Extension
.c- Size
- 1751 bytes
- Lines
- 87
- 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/platform_device.hlinux/regmap.howl-common.h
Detected Declarations
function owl_clk_set_regmapfunction owl_clk_regmap_initfunction owl_clk_probe
Annotated Snippet
if (ret) {
dev_err(dev, "Couldn't register clock %d - %s\n",
i, name);
return ret;
}
}
ret = devm_of_clk_add_hw_provider(dev, of_clk_hw_onecell_get, hw_clks);
if (ret)
dev_err(dev, "Failed to add clock provider\n");
return ret;
}
Annotation
- Immediate include surface: `linux/platform_device.h`, `linux/regmap.h`, `owl-common.h`.
- Detected declarations: `function owl_clk_set_regmap`, `function owl_clk_regmap_init`, `function owl_clk_probe`.
- 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.