dm_test_wb_...ght_mismatch(9)
π¦ 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 π:
dm_test_wb_atomic_check_no_job(9)dm_test_wb_atomic_check_no_fb(9)dm_test_wb_atomic_check_valid(9)dm_test_wb_atomic_check_size_mismatch(9)dm_test_wb_atomic_check_width_mismatch(9)dm_test_wb_atomic_check_invalid_format(9)dm_test_wb_get_modes_returns_modes(9)dm_test_wb_get_modes_bounded_by_max(9)dm_test_wb_connector_init_success(9)dm_test_wb_prepare_job_no_fb(9)dm_test_wb_cleanup_job_no_fb(9)
π reminder bestie: for real though, if the height doesn't matchvdisplay, 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms