dpu_hw_merge_3d_init(9)

💅 dpu_hw_merge_3d_init(9) — from the Kernel API Manual, bestie

Okay so picture this: you're deep in the DRM/msm mines, you've got a merge3d catalog entry in your hand, and you need a driver object for it. That's literally this function's whole job. It initializes the merge_3d driver for the passed merge3d catalog entry ✨

No cap, it's a small one. Let's get into it 🎀

---

✨ SYNOPSIS ✨

struct dpu_hw_merge_3d * dpu_hw_merge_3d_init (struct drm_device *dev ,
const struct dpu_merge_3d_cfg *cfg , void __iomem *addr );

Lowkey the vibe check: it takes three things in, hands you back a struct dpu_hw_merge_3d *. Periodt 💅

---

🌸 ARGUMENTS 🌸

• dev — the corresponding device for devres management 🫶 (yes, devres is doing the cleanup so you don't have to, iconic behaviour honestly)
• cfg — the Pingpong catalog entry for which the driver object is required 🌈 (that's what it says, and I'm not about to rewrite the docs on you, bestie — just relaying the lore fr fr)
• addr — the mapped register io address of MDP 👑

---

🔥 RETURN 🔥

You get either an error code or an allocated dpu_hw_merge_3d context. That's the whole deal — check it, don't just assume it slayed 😭

---

🦋 SEE ALSO 🦋

The kernel file, right here:

./drivers/gpu/drm/msm/disp/dpu1/dpu_hw_merge3d.c

Go read it, it's giving main character energy 💜

---

Heads up bestie: the source lives in ./drivers/gpu/drm/msm/disp/dpu1, it's dated October 2026, and it came straight out of the Kernel API Manual. Drink some water, go touch grass, and may your merges always be 3D 💖🌸✨