dm_test_wb_...ght_mismatch(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ dm_test_wb_...ght_mismatch(9) πŸ¦‹

okay bestie, welcome to the Kernel API Manual ✨ this one's a lil niche but it's giving "very specific unit test" energy and honestly? we stan a focused icon πŸ’…


🌸 NAME 🌸

dm_test_wb_atomic_check_height_mismatch β€” literally just here to verify that things get rejected when the height alone is the thing that differs πŸŽ€


✨ SYNOPSIS ✨

void dm_test_wb_atomic_check_height_mismatch (struct kunit *test );

🫢 ARGUMENTS 🫢

  • test β€” the KUnit test context, iykyk 🌈 it's the lil bundle of test-state that gets handed in so the test can actually do its thing

πŸ’œ DESCRIPTION πŸ’œ

so here's the vibe: when only the framebuffer height differs from the CRTC mode vdisplay, the function should return -EINVAL 😭 like, it's a mismatch, bestie, the function is NOT gonna pretend that's fine. no cap, that's the whole test. one job. iconic behaviour honestly πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

Kernel file:

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

and the rest of the friend group πŸ’–:


πŸ“ reminder bestie: for real though, if the height doesn't match vdisplay, expect -EINVAL. that's the whole point, don't forget it πŸ’€

okay that's the page!! brought to you by the Kernel API Manual, sourced from ./drivers/gpu/drm/amd/display/..., dated October 2026, and filed under dm_test_wb_...ght_mismatch(9) 🧚 mwah, ty for reading, ily, go run your tests πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from