dm_test_fill...clamps_depth(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

Besties, welcome to dm_test_fill...clamps_depth, page 9 of the Kernel API Manual β€” yes the header literally says dm_test_fill...clamps_depth(9) twice and we love a symmetrical moment ✨

The actual star of the show is dm_test_fill_stream_hdmi_ep_clamps_depth β€” a test that checks the HDMI TMDS depth clamp actually gets applied. That's the whole vibe. Slay. πŸ’…


✨ SYNOPSIS ✨

void dm_test_fill_stream_hdmi_ep_clamps_depth (struct kunit *test );

πŸ’… ARGUMENTS πŸ’…

  • test β€” the KUnit test context, aka the little bag of state the test carries around with it. Main character energy, honestly. 🫢

πŸŽ€ DESCRIPTION πŸŽ€

okay so picture this: when is_hdmi_ep is set, the colour depth gets clamped down to whatever the sink's max TMDS clock actually allows. So if you come in asking for a 10bpc request that goes over the limit? It gets reduced to 8bpc. No cap, no drama, just math doing its thing. 🌈


πŸ¦‹ SEE ALSO πŸ¦‹

The kernel file this lives in is ./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_connector_test.c β€” one file, absolute icon. πŸ‘‘

And here's the full squad, all 238 of them, in the exact order they showed up to the group chat (no one got left on read, I promise πŸ’–):


okay that's the whole page bestie πŸ’– it came from ./drivers/gpu/drm/amd/display/... with a date stamp of October 2026, and yeah β€” the footer still says dm_test_fill...clamps_depth(9) because the manual name is literally never beating the repetition allegations. go forth and clamp that depth. periodt. πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from