dm_test_wb_g...eturns_modes(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dm_test_wb_get_modes_returns_modes(9) β€” from the Kernel API Manual, bestie

okay so picture this: it's a KUnit test page, it lives in the Kernel API Manual, and it's literally just here to make sure one (1) function does one (1) thing. short king. iconic behavior. let's get into it 🫢


✨ NAME ✨

dm_test_wb_get_modes_returns_modes β€” the vibe check that confirms at least one mode actually comes back. no cap, that's the whole job πŸ’…


🌸 SYNOPSIS 🌸

void dm_test_wb_get_modes_returns_modes (struct kunit *test );

πŸŽ€ ARGUMENTS πŸŽ€

  • test β€” the KUnit test context, aka the little backpack this test carries its stuff in πŸŽ’

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” this test spins up a DRM mock connector (fake connector, real intentions) and uses it to check that amdgpu_dm_wb_connector_get_modes actually does its thing and populates that connector with at least one display mode.

that's it. that's the whole test. one mode minimum, zero modes = not slaying. ✨

fr fr, "at least one" is the bar here β€” the test isn't asking for a whole lineup, just proof that something comes back. lowkey the most reasonable test in the suite.

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file πŸ“

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

and the rest of the friend group, all showing up to the group chat πŸ’–:


🌈 that's the page!! sourced from ./drivers/gpu/drm/amd/display/..., dated October 2026, and filed under dm_test_wb_g...eturns_modes(9) β€” mwah, go read the other tests, ily bye πŸ’œπŸŽ€

πŸ“¦ where this page comes from