dm_test_wb_...unded_by_max(9)

✨ dm_test_wb_...unded_by_max(9) ✨

okay bestie, welcome to the Kernel API Manual 💅 this one's a lil deep-cut from the AMD display test garden and honestly? it's giving "quietly important" 🎀

💖 NAME 💖

dm_test_wb_get_modes_bounded_by_max — the one that goes "hey, are all these modes actually within max resolution?" and checks, fr fr 🌸

⭐ SYNOPSIS ⭐

void dm_test_wb_get_modes_bounded_by_max (struct kunit *test );

🦋 ARGUMENTS 🦋

• test — your KUnit test context, the little main-character passport this test carries around with it 🫶

🔥 DESCRIPTION 🔥

okay so picture this: the test spins up a DRM mock connector (yes, a mock one, we're not out here touching real hardware, no cap) and then verifies that every single mode handed back by amdgpu_dm_wb_connector_get_modes has hdisplay <= 3840 and vdisplay <= 2160 😌✨

why those numbers? because that's literally the DWB hardware maximum, and the modes gotta match it — nothing bigger sneaking through the vibe check 💀

so: all modes within max. that's the whole assignment. and it ate 👑

👑 SEE ALSO 👑

the kernel file it lives in, in all its glory:

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

and the whole friend group of sibling tests, because they roll deep 🫶:

• 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_height_mismatch(9)
• dm_test_wb_atomic_check_invalid_format(9)
• dm_test_wb_get_modes_returns_modes(9)
• dm_test_wb_connector_init_success(9)
• dm_test_wb_prepare_job_no_fb(9)
• dm_test_wb_cleanup_job_no_fb(9)

---

that's the whole page, bestie 💜 cute lil sign-off time: this came from the source at ./drivers/gpu/drm/amd/display/... and it's dated October 2026, filed under dm_test_wb_...unded_by_max(9) 🌈🍓 go check on those other tests, they miss you 💖