include/drm/bridge/inno_hdmi.h

File Facts

System

Linux kernel

Corpus path

include/drm/bridge/inno_hdmi.h

Extension

.h

Size

797 bytes

Lines

36

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct device
• struct drm_encoder
• struct drm_display_mode
• struct inno_hdmi
• struct inno_hdmi_plat_ops
• struct inno_hdmi_phy_config
• struct inno_hdmi_plat_data

Annotated Snippet

struct inno_hdmi_plat_ops {
	void (*enable)(struct device *pdev, struct drm_display_mode *mode);
};

struct inno_hdmi_phy_config {
	unsigned long pixelclock;
	u8 pre_emphasis;
	u8 voltage_level_control;
};

struct inno_hdmi_plat_data {
	const struct inno_hdmi_plat_ops *ops;
	struct inno_hdmi_phy_config *phy_configs;
	struct inno_hdmi_phy_config *default_phy_config;
};

struct inno_hdmi *inno_hdmi_bind(struct device *pdev,
				 struct drm_encoder *encoder,
				 const struct inno_hdmi_plat_data *plat_data);
#endif /* __INNO_HDMI__ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct device`, `struct drm_encoder`, `struct drm_display_mode`, `struct inno_hdmi`, `struct inno_hdmi_plat_ops`, `struct inno_hdmi_phy_config`, `struct inno_hdmi_plat_data`.
• Atlas domain: Repository Root And Misc / include.
• 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.