drivers/media/cec/platform/s5p/s5p_cec.h

File Facts

System

Linux kernel

Corpus path

drivers/media/cec/platform/s5p/s5p_cec.h

Extension

.h

Size

1707 bytes

Lines

77

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

• linux/clk.h
• linux/interrupt.h
• linux/kernel.h
• linux/mfd/syscon.h
• linux/module.h
• linux/of.h
• linux/platform_device.h
• linux/pm_runtime.h
• linux/timer.h
• linux/workqueue.h
• media/cec.h
• exynos_hdmi_cec.h
• regs-cec.h
• s5p_cec.h

Detected Declarations

• struct cec_notifier
• struct s5p_cec_dev
• enum cec_state

Annotated Snippet

struct s5p_cec_dev {
	struct cec_adapter	*adap;
	struct clk		*clk;
	struct device		*dev;
	struct mutex		lock;
	struct regmap           *pmu;
	struct cec_notifier	*notifier;
	int			irq;
	void __iomem		*reg;

	enum cec_state		rx;
	enum cec_state		tx;
	struct cec_msg		msg;
};

#endif /* _S5P_CEC_H_ */

Annotation

• Immediate include surface: `linux/clk.h`, `linux/interrupt.h`, `linux/kernel.h`, `linux/mfd/syscon.h`, `linux/module.h`, `linux/of.h`, `linux/platform_device.h`, `linux/pm_runtime.h`.
• Detected declarations: `struct cec_notifier`, `struct s5p_cec_dev`, `enum cec_state`.
• 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.