optc1_get_crc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… optc1_get_crc β€” Kernel API Manual, bestie edition ✨

okay so picture this: you're deep in the Kernel API Manual and you stumble on optc1_get_crc, and it's literally the "grab the CRC" girlie. let me put you on. 🫢


🌸 NAME 🌸

optc1_get_crc β€” Capture CRC result per component πŸ’–


✨ SYNOPSIS ✨

bool optc1_get_crc (struct timing_generator *optc , uint8_t idx ,
uint32_t *r_cr , uint32_t *g_y , uint32_t *b_cb );

like, it returns a bool, takes a struct timing_generator *optc, a uint8_t idx, and three uint32_t * out-params. that's the whole vibe check. no cap. πŸ¦‹


πŸŽ€ ARGUMENTS πŸŽ€

  • optc β€” your timing_generator instance. the main character, honestly πŸ‘‘
  • idx β€” index of the crc engine we're pulling the CRC from. which one? that one. iykyk πŸ’…
  • r_cr β€” 16-bit primary CRC signature for red data. red era. πŸ“
  • g_y β€” 16-bit primary CRC signature for green data. green era. 🌈
  • b_cb β€” 16-bit primary CRC signature for blue data. blue era. πŸ¦‹

πŸ”₯ DESCRIPTION πŸ”₯

so what does it do? bestie, it reads the CRC signature straight out of the OPTC registers. and the way that it does it? there are three registers keeping the CRC result per color component (RGB). three registers. red, green, blue. it's giving trio energy and i'm obsessed. 😭✨


⭐ RETURN ⭐

the rules are simple, fr fr:

  • if CRC is disabled β†’ return false πŸ’€
  • otherwise β†’ return true, and the CRC results land in the parameters πŸŽ‰

🌸 SEE ALSO 🌸

kernel file right here: ./drivers/gpu/drm/amd/display/dc/optc/dcn10/dcn10_optc.c πŸ“

and the whole friend group (go read these too, bestie):


ngl this page came from ./drivers/gpu/drm/amd/display/... and it's dated October 2026 β€” slay, future girlie. signing off, mwah πŸ’œπŸ§šβ€β™€οΈ
πŸ“¦ where this page comes from