dm_test_buil..._ranges_mcif(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dm_test_buil..._ranges_mcif(9) 💅

ok so bestie, welcome to the Kernel API Manual — yes that's the manual name, it's giving very official, very serious, and yet here we are about to talk about a KUnit test that pokes at watermark clock ranges. stay with me, it's actually cute 🎀

✨ NAME ✨

dm_test_build_wm_clock_ranges_mcif — the Test writer (MCIF) watermark sets bestie. literally her whole job 🫶

🌸 SYNOPSIS 🌸

void dm_test_build_wm_clock_ranges_mcif (struct kunit *test );

🦋 ARGUMENTS 🦋

  • test — the KUnit test context. that's it. that's the whole argument. she's low-maintenance, we love her 💖

🔥 DESCRIPTION 🔥

okay so here's the vibe check 👑

This test verifies that build_wm_clock_ranges_soc15 copies the writer set count and maps the writer clocks into the MCIF ranges. no cap, that's exactly what it does.

And the mapping? iconic:

  • fill clocks become socclk ⭐
  • drain clocks become mem clk ⭐

and each one gets converted from MHz to kHz. yes bestie, units matter, don't come for me 😭🙈

👑 SEE ALSO 👑

💜 Kernel file

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

🧚 The whole group chat (every single sibling, no one left out)

ok that's the whole page bestie, you ate that 💅 no notes, fr fr

mwah 💋 — this cutie came from ./drivers/gpu/drm/amd/display/..., dated October 2026, and she's filed under dm_test_buil..._ranges_mcif(9) so you can find her again. bye bestie, slay your tests 🌈💖

📦 where this page comes from