vc4_mock_atomic_add_output(9)

💅 vc4_mock_atomic_add_output(9) — a Kernel API Manual moment ✨

okay so bestie, welcome to the glow-up era of the kernel API manual 🎀 this one lives in the Kernel API Manual family, and it's literally about turning an output on in an atomic state. no cap.

---

🌸 NAME 🌸

vc4_mock_atomic_add_output — enables an output in a state</p> 💖 yes queen, that's the whole bit.

---

✨ SYNOPSIS ✨

int vc4_mock_atomic_add_output (struct kunit *test , struct drm_atomic_commit *state , enum vc4_encoder_type type );

---

🫶 ARGUMENTS 🫶

• test — the test context object 🧪 like, the lil world this whole call is happening inside.
• state — the atomic state you wanna enable the output in. this is the state bestie ✨
• type — the type of the output encoder 👑 tell it what kind of encoder you're working with.

---

💫 DESCRIPTION 💫

so what it actually does: it adds an output CRTC and connector to a state, and then enables them 🔥 both of them. not one, both. we love a two-for-one slay.

CRTC + connector = added and enabled, periodt.

---

💀 RETURN 💀

• 0 — success, we ate 💅
• a negative error code — failure, and honestly 😭

⚠️ okay this part is important, no skipping: if the error is EDEADLK, the entire atomic sequence must be restarted. like, the whole thing. from the top. all other errors are fatal — not a vibe check you can ignore, fr fr.

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/vc4/tests/vc4_mock_output.c 🦋 go read the source, iykyk
• vc4_mock_atomic_del_output(9) — the opposite bestie, the one that removes instead of adds 🧚 the duality of woman

---

mwah 💋 that's the page! it's giving kernel, it's giving mock, it's giving atomic output enabling energy. this lil slice of documentation comes to you from ./drivers/gpu/drm/vc4/tests, dated October 2026, and it's filed under vc4_mock_atomic_add_output(9) — stan the vc4 tests directory for clear skin ⭐💜