mtk_drm_of_...th_build_one(9)

🫶 mtk_drm_of_...th_build_one(9) 🫶

okay so welcome to the Kernel API Manual, bestie — this is the page for mtk_drm_of_...th_build_one(9), and the actual function it’s about is mtk_drm_of_ddp_path_build_one. yes, the title is a little cryptic, but we move 💅

💖 NAME 💖

mtk_drm_of_ddp_path_build_one — Build a Display HW Pipeline for a CRTC Path

✨ SYNOPSIS ✨

int mtk_drm_of_ddp_path_build_one (struct device *dev , enum
mtk_crtc_path cpath , const unsigned int **out_path , unsigned int
*out_path_len );

🎀 ARGUMENTS 🎀

• dev — The mediatek-drm device
• cpath — CRTC Path relative to a VDO or MMSYS
• out_path — Pointer to an array that will contain the new pipeline
• out_path_len — Number of entries in the pipeline array

🌸 DESCRIPTION 🌸

okay so MediaTek SoCs are kinda extra in the best way: they can use different DDP hardware pipelines (or paths) depending on the board-specific desired display configuration. This function literally walks through all of the output endpoints starting from a VDO or MMSYS hardware instance and builds the right pipeline as specified in device trees. main character energy fr fr 🦋

🔥 RETURN 🔥

• 0 — Display HW Pipeline successfully built and validated
• -ENOENT — Display pipeline was not specified in device tree
• -EINVAL — Display pipeline built but validation failed
• -ENOMEM — Failure to allocate pipeline array to pass to the caller

🦋 SEE ALSO 🦋

• Kernel file ./drivers/gpu/drm/mediatek/mtk_drm_drv.c

and that’s the whole page, bestie 💜 this one lives under ./drivers/gpu/drm/mediatek, it’s dated October 2026, and the footer wraps up with mtk_drm_of_...th_build_one(9) — periodt ✨🎀