dm_test_com...ack_addition(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dm_test_commit_audio_skips_writeback_addition — Kernel API Manual

okay so bestie, welcome to the Kernel API Manual 🌸 we're about to vibe through a KUnit test whose name is genuinely a whole paragraph, and honestly? it ate. the man page header is dm_test_com...ack_addition(9) (yes it's truncated, yes that's just how it is, we're not fixing it, it's iconic that way) 🎀

✨ NAME ✨

dm_test_commit_audio_skips_writeback_addition — the test that checks writeback addition gets skipped. like, no writeback audio for you, bestie 🚫🔊

🦋 SYNOPSIS 🦋

void dm_test_commit_audio_skips_writeback_addition (struct kunit *test
);

that's it. one function. void return. very demure, very mindful ✨

💜 ARGUMENTS 💜

  • test — the KUnit test context. that's the whole vibe, it's the scaffolding that holds the test together 💅

🔥 DESCRIPTION 🔥

so here's the tea, and it's kind of important 😭 so listen up:

Even when you've got a valid modeset and the stream status is looking all good — like, everything's passing the vibe check — writeback connectors still must not publish an HDA audio instance. periodt. 🙅‍♀️

not me explaining this twice, but fr fr: valid modeset ✅, stream status ✅, HDA audio instance for writeback connectors ❌. the whole point of the test is that the skip happens anyway. it's giving strict boundaries, and we love that for us 👑

🌈 SEE ALSO 🌈

first up, the actual kernel file this lives in (iykyk):

  • ./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_audio_test.c 📁

and now the whole friend group — the squad of sibling tests, all listed exactly like this:

like, that's the whole group chat right there 🫶 no cap, they all get along.

sign-off time, besties 🧚💖 this page came from ./drivers/gpu/drm/amd/display/... and the version stamp is October 2026 — and yeah the footer still says dm_test_com...ack_addition(9) because some things never change 💀 stay slay, go read your kernel source, mwah 💋✨

📦 where this page comes from