drivers/gpu/drm/meson/meson_vclk.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/meson/meson_vclk.h

Extension

.h

Size

950 bytes

Lines

38

Domain

Driver Families

Bucket

drivers/gpu

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

• drm/drm_modes.h

Detected Declarations

• struct meson_drm

Annotated Snippet

#ifndef __MESON_VCLK_H
#define __MESON_VCLK_H

#include <drm/drm_modes.h>

struct meson_drm;

enum {
	MESON_VCLK_TARGET_CVBS = 0,
	MESON_VCLK_TARGET_HDMI = 1,
	MESON_VCLK_TARGET_DMT = 2,
};

/* 27MHz is the CVBS Pixel Clock */
#define MESON_VCLK_CVBS			(27 * 1000 * 1000)

enum drm_mode_status
meson_vclk_dmt_supported_freq(struct meson_drm *priv, unsigned long long freq);
enum drm_mode_status
meson_vclk_vic_supported_freq(struct meson_drm *priv,
			      unsigned long long phy_freq,
			      unsigned long long vclk_freq);

void meson_vclk_setup(struct meson_drm *priv, unsigned int target,
		      unsigned long long phy_freq, unsigned long long vclk_freq,
		      unsigned long long venc_freq, unsigned long long dac_freq,
		      bool hdmi_use_enci);

#endif /* __MESON_VCLK_H */

Annotation

• Immediate include surface: `drm/drm_modes.h`.
• Detected declarations: `struct meson_drm`.
• Atlas domain: Driver Families / drivers/gpu.
• 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.