dm_test_dmu...t_no_fb_info(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dm_test_dmub_hw_init_no_fb_info(9) — like, the Kernel API Manual entry, bestie ✨

okay so picture this: it's a page straight out of the Kernel API Manual, and it's all about one single little KUnit test. tiny page, big "what happens when the vibes are missing" energy. let's go 🫶

🌸 NAME 🌸

dm_test_dmub_hw_init_no_fb_info — the test that proves hw init straight-up fails when there's no framebuffer info. like, no fb info, no hw init, that's the whole plot 🎬

✨ SYNOPSIS ✨

void dm_test_dmub_hw_init_no_fb_info (struct kunit *test );

🎀 ARGUMENTS 🎀

  • test — the KUnit test context 💖 that's literally it, that's the whole arg list.

🦋 DESCRIPTION 🦋

so here's the scenario: a DMUB service is present, but there's no framebuffer info to be found anywhere. in that exact situation, dm_dmub_hw_init should return -EINVAL. yes bestie, that's the assertion, and honestly? iconic behaviour. the test exists purely to make sure the failure path goes off the way it's supposed to 🔥 periodt.

👑 SEE ALSO 👑

Kernel file

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

and the whole squad of sibling tests, no cap — every single one of them:

💀 real talk: if you're hunting through this list at 2am, drink some water. hydration is self-care.

and that's the page! 🧚‍♀️ it ships out of ./drivers/gpu/drm/amd/display/... and it's dated October 2026 — so when you see it, just know the Kernel API Manual said it first. bye bestie, go write some tests 💜🎀✨

📦 where this page comes from