dm_test_funcs_force_no_edid(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dm_test_funcs_force_no_edid(9) — from the Kernel API Manual, bestie ✨

okay so this is a page straight out of the Kernel API Manual, and the star of the show is dm_test_funcs_force_no_edid(9). yes the title is a mouthful, no we're not shortening it, it's iconic and we respect it 🫶

✨ NAME ✨

dm_test_funcs_force_no_edid — literally just a test that force() leaves drm_edid <rainbow>NULL</rainbow> when there's no EDID. that's the whole vibe check 🎀

🌸 SYNOPSIS 🌸

void dm_test_funcs_force_no_edid (struct kunit *test );

🦋 ARGUMENTS 🦋

  • test — the KUnit test context. that's it, that's the whole argument list, she's low-maintenance 💅

💖 DESCRIPTION 💖

k so picture this: a headless force-on DisplayPort connector — headless meaning no screen attached, nobody home, the lights are off 😭 — and because of that it reads no EDID. so after the force callback does its little run, the cached drm_edid pointer has to stay NULL. not sorta-null. not stale-pointer-null. NULL-null. no cap 🫶

that's the entire test. it's giving "small but mighty" and honestly? obsessed ✨

ngl, this one's a real one — if drm_edid comes back not-NULL after force() on a no-EDID connector, the test has officially flopped and it's giving red flags 🚩

🔥 SEE ALSO 🔥

Kernel file 👑 (./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_connector_test.c) — that's the whole squad's home turf, bestie 🏠

and now the entire friend group, in the exact order they showed up, because nobody gets left out of the group chat:

and that's the whole thing, bestie 🌈 this page lives over at ./drivers/gpu/drm/amd/display/... and it's dated October 2026 — so yeah, future vibes only 💜✌️ go forth and keep that drm_edid NULL, mwah 💋

📦 where this page comes from