intel_cdclk_clock_changed(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… intel_cdclk_clock_changed β€” like, did the clock actually change bestie? πŸ‘€

okay so real talk, this one lives in the Kernel API Manual and honestly it's giving "tiny function, huge responsibility." Let's get into it ✨


🌸 NAME 🌸

intel_cdclk_clock_changed β€” check whether the clock changed πŸ•πŸ’«


πŸ¦‹ SYNOPSIS πŸ¦‹

bool intel_cdclk_clock_changed (const struct intel_cdclk_config *a ,
const struct intel_cdclk_config *b );

like yes that's the whole vibe. two configs walk in, a bool walks out 😌


πŸŽ€ ARGUMENTS πŸŽ€

  • a β€” the first CDCLK configuration. bestie number one πŸ’–
  • b β€” the second CDCLK configuration. bestie number two 🫢

⭐ RETURN ⭐

Returns True if CDCLK changed in a way that requires re-programming, and False otherwise.

so like… True means "oop, we gotta re-program this", False means "we're so chill, nothing to do here" πŸ’… no cap, that's the whole answer.

ngl this is one of those "small function, do not skip the details" situations β€” the "in a way that requires re-programming" part is the whole point, don't flatten it πŸ™ˆ

🌈 SEE ALSO 🌈

okay this list is long but we're doing it, every single one, no skipping, periodt πŸ‘‘

like, the whole cdclk friend group showed up 🧚✨ iykyk


and that's the page!! mwah πŸ’‹ this gem comes to you from ./drivers/gpu/drm/i915/display, dated October 2026, straight outta the Kernel API Manual β€” go read the source babes, it's iconic πŸŒŸπŸ’œ

πŸ“¦ where this page comes from