dm_test_even...en_encrypted(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so bestie, welcome to dm_test_event_property_update_enabled_when_encrypted β€” from the Kernel API Manual, no less πŸ’… β€” and the whole entire vibe of this one is: encrypted maps to ENABLED. that's it. that's the page. 🫢


🌸 SYNOPSIS 🌸

like, here's the exact shape of it, fr fr:

void dm_test_event_property_update_enabled_when_encrypted (struct kunit
       *test );

πŸŽ€ ARGUMENTS πŸŽ€

  • test β€” the KUnit test context πŸ’– (yes, that's the whole argument list, she's low maintenance)

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this: a fully connected display πŸ‘‘ running TYPE0 content with HDCP1 encryption on top. that combo drives the connected path, and the way hdcp_get_content_protection_from_status reports it? it comes back as DRM_MODE_CONTENT_PROTECTION_ENABLED. iconic behavior, honestly. ✨

and because the test is set up before anything gets messy, the connector state is pre-set to ENABLED β€” so when drm_hdcp_update_content_protection rolls up, it just... leaves it unchanged. nothing to see here, the vibe is already correct πŸ’€πŸŒΈ

no cap: the whole point is that the state starts as ENABLED and stays ENABLED β€” don't go expecting a change, that's literally the test πŸŽ€

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file where all the magic lives, bestie:

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

and here's the full squad β€” every single one of them, i'm not skipping a single name, periodt πŸ’…:


🌈 and that's the page!! source is ./drivers/gpu/drm/amd/display/... and she's stamped October 2026, filed under dm_test_even...en_encrypted(9) β€” go read the other tests bestie, they're all waiting for you πŸ’œπŸŽ€βœ¨

πŸ“¦ where this page comes from