dm_test_wb_...init_success(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dm_test_wb_connector_init_success

okay bestie, welcome to the Kernel API Manual ✨ — section 9, because we're deep in kernel-land and this is the writeback test tea 🫖

🌸 NAME 🌸

dm_test_wb_connector_init_success — the one where we verify writeback connector initialization 💖

🎀 SYNOPSIS 🎀

void dm_test_wb_connector_init_success (struct kunit *test );

that's it. one function, zero drama, maximum slay ✨

🦋 ARGUMENTS 🦋

  • test — the KUnit test context 🧪 like, this is the little test-world this function lives in, standard KUnit stuff, no notes 💅

⭐ DESCRIPTION ⭐

okay so here's the vibe: this test spins up a DRM mock device that's embedded right inside a struct amdgpu_device, and then it verifies a whole checklist of things about amdgpu_dm_wb_connector_init 🫶

it's checking that the init function actually:

  • initializes the writeback connector 👑 (like, the connector exists and it's init'd, periodt)
  • stores the DC link 🔗 (yes, the link is saved, no cap)
  • installs connector state through reset 🌈 (through reset specifically, iykyk)
  • wires the expected DRM callbacks 🔥 (all the callbacks hooked up the way they should be)

so basically: if the init does anything funky with the connector, the DC link, the reset-path state, or the callback wiring — this test catches it 💀 and that's the whole point, bestie 💜

🔍 SEE ALSO 🔍

Kernel file 📁

./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_wb_test.c

and the rest of the writeback test fam — go read these too, they're all iconic 👑:

ngl the whole writeback test suite is lowkey a mood, and this one's the entry point 🧚✨

and that's the page, bestie 💖 this came out of ./drivers/gpu/drm/amd/display/... with a very cute October 2026 date on it — so go forth, run the test, and let it slay 🌈🎀🦋

📦 where this page comes from