vsp1_du_enable(9)

💅 vsp1_du_enable — kernel API manual, but make it make sense 🎀

okay bestie, so the title of this whole situation is vsp1_du_enable and it lives in the Kernel API Manual (yes, the (9) is the section, we love a numbered era). Buckle up, this one's about waking up a display pipeline 🦋

---

✨ NAME ✨

vsp1_du_enable — setup and enable a DU pipeline. that's it, that's the whole vibe: set it up, turn it on, slay 💅

---

🌸 SYNOPSIS 🌸

int vsp1_du_enable (struct device *dev , unsigned int pipe_index ,
                    const struct vsp1_du_lif_config *cfg );

like, three args, one int return, very demure, very mindful ✨

---

🫶 ARGUMENTS 🫶

• dev — the VSP device. your main character right here 👑
• pipe_index — the DRM pipeline index. which pipeline are we doing bestie, pick one 🎀
• cfg — the LIF configuration. the whole blueprint, fr fr 💖

---

🔥 DESCRIPTION 🔥

So what this does is configure the output part of the VSP DRM pipeline for the frame described by cfg.width and cfg.height. Not me getting emotional over a width and height. 😭

It sets up formats on the BRx source pad, the WPF sink and source pads, and the LIF sink pad — and then it starts the pipeline. boom. pipeline started. we're live 🌈

The pipe_index argument selects which DRM pipeline gets set up. and like, how many pipelines are available? that depends on the VSP instance. no cap, it's per-instance, so don't come for me asking for a fixed number 💀

Now here's the niche lore, iykyk: because the media bus code on the blend unit source pad is conditioned by the configuration of its sink 0 pad, we also set up the formats on all blend unit sinks — even if that configuration is gonna get overwritten later by vsp1_du_setup_rpf. like yes it's getting replaced but babe, it still matters, because this makes sure the blend unit configuration is set to a well defined state ✨ iconic defensive programming honestly

Return 0 on success, or a negative error code on failure. that's the whole contract, bestie, respect it 🫶

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/media/platform/renesas/vsp1/vsp1_drm.c — go read the source, it's literally right there 👀
• vsp1_du_disable(9)
• vsp1_du_atomic_begin(9)
• vsp1_du_atomic_update(9)
• vsp1_du_atomic_flush(9)

the whole friend group, all linked up 🧚💜

---

and that's the page!! mwah 💋 it came from ./drivers/media/platform/renes... (the source path, slightly truncated like a cute little teaser) with the version tag vsp1_du_enable(9), dated October 2026 — yes, October 2026, we're manifesting the future, periodt ⭐🌸🍓