drm_color_lut_check(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_color_lut_check(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so this is drm_color_lut_check(9), straight out of the kernel API manual, and it's literally the vibe check for your lookup table ✨


🌸 NAME 🌸

drm_color_lut_check β€” check validity of lookup table. that's it, that's the whole job, and it does it slayfully πŸ’…


✨ SYNOPSIS ✨

int drm_color_lut_check (const struct drm_property_blob *lut , u32 tests );

🫢 ARGUMENTS 🫢

  • lut β€” the property blob containing the LUT we're checking. yes bestie, the actual table, right there in a blob, iconic πŸ¦‹
  • tests β€” a bitmask of tests to run. not a single test, a whole bitmask of them, we're doing the full battery πŸ”₯

πŸ’– DESCRIPTION πŸ’–

so this is the helper that checks whether a userspace-provided lookup table is valid and satisfies the hardware requirements. like, does this table actually make sense, will the hardware be okay with it, all of that 🧚

drivers pass in a bitmask indicating which of the tests in drm_color_lut_tests should be performed β€” so you pick your lineup of tests, no cap 🌈

it returns 0 on success, and -EINVAL on failure 😭 (as it should, honestly β€” invalid is invalid).

ngl, -EINVAL is the moment of truth. if you see it, the table did not pass the vibe check πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group, fr fr β€” every one of these is linked and every one of them matters πŸ“


and that's the page, bestie πŸ’œ it lives in ./drivers/gpu/drm and this particular glow-up is dated October 2026 β€” go off, kernel docs, periodt πŸ‘‘βœ¨

πŸ“¦ where this page comes from