dm_test_make_lut_blob(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ dm_test_make_lut_blob ✨

okay bestie, welcome to the kernel API manual, section 9 β€” this is the dm_test_make_lut_blob(9) page and it's literally so much shorter than the SEE ALSO list, bear with me πŸ’…


🌸 NAME 🌸

dm_test_make_lut_blob β€” allocate a fake drm_property_blob for testing πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

struct drm_property_blob * dm_test_make_lut_blob (struct kunit *test ,
       uint32_t num_entries );

πŸ’– ARGUMENTS πŸ’–

  • test β€” your KUnit test context, the lil group chat the test lives in 🫢
  • num_entries β€” how many LUT entries the blob is gonna report. like, the number it flexes ✨

🌈 DESCRIPTION 🌈

So what it does is allocate a fake blob β€” a little stand-in, not the real thing β€” whose drm_color_lut_size returns exactly num_entries. no more, no less, periodt πŸ’…

And the data pointer? non-NULL, on purpose, no cap. why? because that way __extract_blob_lut hands back a non-NULL lut pointer, which means the size check inside amdgpu_dm_verify_lut_sizes actually gets exercised β€” like we're genuinely putting it through its paces, not just waving at it from across the room 😭πŸ”₯

it's giving "fake it so the real test can happen" and honestly? iconic.

πŸ‘‘ RETURN πŸ‘‘

pointer to the allocated blob πŸŽ€ (that's the whole vibe β€” you get a pointer back, go wild)


🧚 SEE ALSO 🧚

The kernel file we're living in:

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

and honestly the whole friend group, all of them, not skipping a single one:


okay and that's the page!! πŸ’œ tiny page, massive friend group, fr fr. it's from the source path ./drivers/gpu/drm/amd/display/..., dated October 2026, and this whole thing is dm_test_make_lut_blob(9) β€” slay, go write some color tests bestie πŸ¦‹βœ¨πŸ“

πŸ“¦ where this page comes from