intel_dpll_dump_hw_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ intel_dpll_dump_hw_state(9) ✨

okay so bestie, welcome to the intel_dpll_dump_hw_state(9) page from the Kernel API Manual πŸ’… this is a little function in the i915 display code and honestly it's giving "quietly essential" β€” it just dumps out the hardware state for you. no drama, no cap.


🌸 NAME 🌸

intel_dpll_dump_hw_state β€” dump that hw_state, periodt πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

void intel_dpll_dump_hw_state (struct intel_display *display , struct
       drm_printer *p , const struct intel_dpll_hw_state *dpll_hw_state );

like, it returns void β€” nothing comes back out, it's purely a "print it and go" situation πŸŽ€


πŸ’œ ARGUMENTS πŸ’œ

  • display β€” the intel_display structure, your main character of the moment πŸ‘‘
  • p β€” where to print the state to, i.e. the drm_printer that's catching all the output πŸ–¨οΈβœ¨
  • dpll_hw_state β€” the hw state to be dumped, the actual star of the show 🌟

🧚 DESCRIPTION 🧚

"Dumo out" the relevant values in dpll_hw_state β€” yes, that typo is literally in the original and I'm keeping it because it's iconic πŸ˜­πŸ’€ anyway: it prints out the relevant values from dpll_hw_state so you can actually see what the hardware is up to. lowkey so useful, highkey underrated 🫢


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/gpu/drm/i915/display/intel_dpll_mgr.c β€” that's where the magic lives, iykyk πŸ’…

and the whole dpll bestie squad, in order, no one left behind:


fr fr, go read intel_dpll_compare_hw_state(9) after this one, they're a matched set πŸ“

and that's the whole page bestie, you ate that πŸŽ€ sign-off time: this one lives in ./drivers/gpu/drm/i915/display, and the page is dated October 2026 πŸ’–βœ¨ slay, bye! πŸŒˆπŸ¦‹

πŸ“¦ where this page comes from