drivers/dpll/zl3073x/chan.c

File Facts

System

Linux kernel

Corpus path

drivers/dpll/zl3073x/chan.c

Extension

.c

Size

5050 bytes

Lines

193

Domain

Driver Families

Bucket

drivers/dpll

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/cleanup.h
• linux/dev_printk.h
• linux/string.h
• linux/types.h
• chan.h
• core.h

Detected Declarations

• function zl3073x_chan_state_update
• function zl3073x_chan_state_fetch
• function zl3073x_chan_state_set

Annotated Snippet

if (dchan->ref_prio[i] != chan->ref_prio[i]) {
			rc = zl3073x_write_u8(zldev,
					      ZL_REG_DPLL_REF_PRIO(i),
					      chan->ref_prio[i]);
			if (rc)
				return rc;
		}
	}

	/* Commit DPLL configuration */
	rc = zl3073x_mb_op(zldev, ZL_REG_DPLL_MB_SEM, ZL_DPLL_MB_SEM_WR,
			   ZL_REG_DPLL_MB_MASK, BIT(index));
	if (rc)
		return rc;

	/* After successful write store new state */
	dchan->cfg = chan->cfg;

	return 0;
}

Annotation

• Immediate include surface: `linux/cleanup.h`, `linux/dev_printk.h`, `linux/string.h`, `linux/types.h`, `chan.h`, `core.h`.
• Detected declarations: `function zl3073x_chan_state_update`, `function zl3073x_chan_state_fetch`, `function zl3073x_chan_state_set`.
• Atlas domain: Driver Families / drivers/dpll.
• 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.