drivers/gpu/drm/omapdrm/dss/hdmi5_core.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/omapdrm/dss/hdmi5_core.h

Extension

.h

Size

10762 bytes

Lines

296

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

• hdmi.h

Detected Declarations

• struct hdmi_core_vid_config
• struct csc_table
• enum hdmi_core_packet_mode

Annotated Snippet

struct hdmi_core_vid_config {
	struct hdmi_config v_fc_config;
	enum hdmi_core_packet_mode packet_mode;
	int data_enable_pol;
	int vblank_osc;
	int hblank;
	int vblank;
};

struct csc_table {
	u16 a1, a2, a3, a4;
	u16 b1, b2, b3, b4;
	u16 c1, c2, c3, c4;
};

void hdmi5_core_ddc_init(struct hdmi_core_data *core);
int hdmi5_core_ddc_read(void *data, u8 *buf, unsigned int block, size_t len);
void hdmi5_core_ddc_uninit(struct hdmi_core_data *core);

void hdmi5_core_dump(struct hdmi_core_data *core, struct seq_file *s);
void hdmi5_configure(struct hdmi_core_data *core, struct hdmi_wp_data *wp,
			struct hdmi_config *cfg);
int hdmi5_core_init(struct platform_device *pdev, struct hdmi_core_data *core);

int hdmi5_audio_config(struct hdmi_core_data *core, struct hdmi_wp_data *wp,
			struct omap_dss_audio *audio, u32 pclk);
#endif

Annotation

• Immediate include surface: `hdmi.h`.
• Detected declarations: `struct hdmi_core_vid_config`, `struct csc_table`, `enum hdmi_core_packet_mode`.
• 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.