intel_set_cd...plane_update(9)
π intel_set_cdclk_pre_plane_update
okay so bestie, welcome to the Kernel API Manual π β yes we're reading kernel docs for fun now, this is who we are, and honestly? iconic behavior.
β¨ NAME β¨
intel_set_cdclk_pre_plane_update β the lil function that pushes the CDCLK state to the hardware π«Ά
πΈ SYNOPSIS πΈ
void intel_set_cdclk_pre_plane_update (struct intel_atomic_state *state
);
that's it. that's the whole signature. she's a void, she returns nothing, she simply does π
π¦ ARGUMENTS π¦
stateβ the intel atomic state, aka the main character of this whole operation π
π DESCRIPTION π
so basically: this function programs the hardware before the HW plane state gets updated, and it does that based on the new CDCLK state β if necessary. key phrase ngl, "if necessary" is doing a lot of heavy lifting there π
so the whole vibe is: new CDCLK state comes in β hardware gets programmed first β then the plane state update happens. order matters, she's a pre-flight girlie β¨
π₯ SEE ALSO π₯
- Kernel file
./drivers/gpu/drm/i915/display/intel_cdclk.cβ this is where she lives, go say hi π CDCLK / RAWCLK(9)intel_cdclk_init_hw(9)intel_cdclk_uninit_hw(9)intel_cdclk_clock_changed(9)intel_cdclk_can_cd2x_update(9)intel_cdclk_changed(9)intel_set_cdclk_post_plane_update(9)β yes she has a sister, the post one, the way that name is literally the inverse πintel_update_max_cdclk(9)intel_update_cdclk(9)intel_read_rawclk(9)intel_init_cdclk_hooks(9)
lowkey reminder bestie: the pre and the post versions are different functions, do not mix them up, that would be a vibe check failure fr fr π
okay that's the page!! it came from ./drivers/gpu/drm/i915/display, dated October 2026, and it's filed under intel_set_cd...plane_update(9) β yes the title is truncated with dots, no I don't know why, and yes it's still slaying πβ¨ byeee π¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms