drivers/clk/versatile/icst.c

Source file repositories/reference/linux-study-clean/drivers/clk/versatile/icst.c

File Facts

System: Linux kernel
Corpus path: drivers/clk/versatile/icst.c
Extension: .c
Size: 2342 bytes
Lines: 103
Domain: Driver Families
Bucket: drivers/clk
Inferred role: Driver Families: exported/initcall integration point
Status: integration 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.
Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

linux/module.h
linux/kernel.h
asm/div64.h
icst.h

Detected Declarations

function icst_hz
function icst_hz_to_vco
export icst307_s2div
export icst525_s2div
export icst_hz
export icst307_idx2s
export icst525_idx2s
export icst_hz_to_vco

Annotated Snippet

if ((unsigned)f_diff < best) {
			vco.v = vd - 8;
			vco.r = rd - 2;
			if (f_diff == 0)
				break;
			best = f_diff;
		}
	}

	return vco;
}

EXPORT_SYMBOL(icst_hz_to_vco);

Annotation

Immediate include surface: `linux/module.h`, `linux/kernel.h`, `asm/div64.h`, `icst.h`.
Detected declarations: `function icst_hz`, `function icst_hz_to_vco`, `export icst307_s2div`, `export icst525_s2div`, `export icst_hz`, `export icst307_idx2s`, `export icst525_idx2s`, `export icst_hz_to_vco`.
Atlas domain: Driver Families / drivers/clk.
Implementation status: integration 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.