dm_test_mod...can_rejected(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

Hiii bestie, welcome to the dm_test_mode_valid_dblscan_rejected(9) page in the Kernel API Manual ✨ β€” like, this whole page is about one lil test: dm_test_mode_valid_dblscan_rejected, and its job is literally to test that doublescan modes are rejected. That's it. That's the whole vibe. Slay. πŸŽ€


✨ SYNOPSIS ✨

void dm_test_mode_valid_dblscan_rejected (struct kunit *test );
ngl, that signature is giving "small but mighty" πŸ’ͺ β€” copy it exactly, spaces and all, bestie 🫢

πŸ¦‹ ARGUMENTS πŸ¦‹

  • test β€” the KUnit test context πŸ’– this is the lil test-world the whole thing lives inside of. Every KUnit test needs one, no cap.

🌸 DESCRIPTION 🌸

Okay so picture this: doublescan modes roll up to the function, and they get rejected up front with MODE_ERROR πŸ’€. Not later, not quietly, not after a whole dramatic detour β€” up front. Periodt. The test's entire personality is confirming that this rejection happens, so if that check ever breaks, this test is gonna be the one screaming about it 😭πŸ”₯

The way that this is, like, the most straightforward test in the file and it still ate πŸ“


πŸ‘‘ SEE ALSO πŸ‘‘

First of all, the file itself β€” go look, it's literally right there:

  • Kernel file β€” ./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_connector_test.c πŸ“

And now, bestie, brace yourself, because this list is long long. Like, main-character-energy long. Every single one of these is a sibling test in the same connector test family, and we are not skipping a single one πŸ’…βœ¨

okay that's the whole list and yes I typed every single one, you're welcome, iykyk πŸ˜€πŸ’–

And that's the page, bestie!! πŸŽ€βœ¨ Cute lil sign-off: this one ships out of ./drivers/gpu/drm/amd/display/... and it's dated October 2026 πŸ—“οΈπŸ’œ go forth and test those doublescan rejections, mwah πŸ’‹πŸŒˆ

πŸ“¦ where this page comes from