drivers/media/i2c/aptina-pll.h
Source file repositories/reference/linux-study-clean/drivers/media/i2c/aptina-pll.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/i2c/aptina-pll.h- Extension
.h- Size
- 865 bytes
- Lines
- 44
- Domain
- Driver Families
- Bucket
- drivers/media
- 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
- No C-style include directives detected by the generator.
Detected Declarations
struct aptina_pllstruct aptina_pll_limitsstruct device
Annotated Snippet
struct aptina_pll {
unsigned int ext_clock;
unsigned int pix_clock;
unsigned int n;
unsigned int m;
unsigned int p1;
};
struct aptina_pll_limits {
unsigned int ext_clock_min;
unsigned int ext_clock_max;
unsigned int int_clock_min;
unsigned int int_clock_max;
unsigned int out_clock_min;
unsigned int out_clock_max;
unsigned int pix_clock_max;
unsigned int n_min;
unsigned int n_max;
unsigned int m_min;
unsigned int m_max;
unsigned int p1_min;
unsigned int p1_max;
};
struct device;
int aptina_pll_calculate(struct device *dev,
const struct aptina_pll_limits *limits,
struct aptina_pll *pll);
#endif /* __APTINA_PLL_H */
Annotation
- Detected declarations: `struct aptina_pll`, `struct aptina_pll_limits`, `struct device`.
- Atlas domain: Driver Families / drivers/media.
- 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.