drivers/media/platform/mediatek/mdp3/mtk-mdp3-cmdq.h

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/mediatek/mdp3/mtk-mdp3-cmdq.h

Extension

.h

Size

961 bytes

Lines

44

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/platform_device.h
• linux/videodev2.h
• linux/soc/mediatek/mtk-cmdq.h
• mtk-img-ipi.h

Detected Declarations

• struct mdp_cmdq_param
• struct mdp_cmdq_cmd
• struct mdp_dev

Annotated Snippet

struct mdp_cmdq_param {
	struct img_config *config;
	struct img_ipi_frameparam *param;
	const struct v4l2_rect *composes[IMG_MAX_HW_OUTPUTS];

	void (*cmdq_cb)(struct cmdq_cb_data data);
	void *cb_data;
	void *mdp_ctx;
};

struct mdp_cmdq_cmd {
	struct work_struct auto_release_work;
	struct cmdq_pkt pkt;
	s32 *event;
	struct mdp_dev *mdp;
	struct cmdq_cb_data *data;
	void (*user_cmdq_cb)(struct cmdq_cb_data data);
	void *user_cb_data;
	struct mdp_comp *comps;
	void *mdp_ctx;
	u8 num_comps;
	u8 pp_idx;
};

struct mdp_dev;

int mdp_cmdq_send(struct mdp_dev *mdp, struct mdp_cmdq_param *param);

#endif  /* __MTK_MDP3_CMDQ_H__ */

Annotation

• Immediate include surface: `linux/platform_device.h`, `linux/videodev2.h`, `linux/soc/mediatek/mtk-cmdq.h`, `mtk-img-ipi.h`.
• Detected declarations: `struct mdp_cmdq_param`, `struct mdp_cmdq_cmd`, `struct mdp_dev`.
• 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.