xe_guc_pc_get_cur_freq(9)
β¨ NAME β¨
xe_guc_pc_get_cur_freq β Get Current requested frequency
okay bestie, quick vibe check: this page is from the Kernel API Manual, and the main character is xe_guc_pc_get_cur_freq(9) β it is literally here to get the current requested frequency. no cap π
π¦ SYNOPSIS π¦
int xe_guc_pc_get_cur_freq (struct xe_guc_pc *pc , u32 *freq );
π ARGUMENTS π
pcβ The GuC PC. yes, that exact struct from the synopsis, bestie π«Άfreqβ A pointer to au32where the freq value will be returned. itβs giving output-parameter energy β¨
π RETURN π
0on success π-EAGAINif GuC PC not ready (likely in middle of a reset).
okay so if you see -EAGAIN, the GuC PC is not ready β and the manual says thatβs likely because itβs in the middle of a reset. not me being dramatic, that is literally the caveat π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/xe/xe_guc_pc.c GuC Power Conservation (PC)(9)xe_guc_pc_action_set_param(9)xe_guc_pc_action_unset_param(9)xe_guc_pc_get_act_freq(9)xe_guc_pc_get_cur_freq_fw(9)xe_guc_pc_get_rp0_freq(9)xe_guc_pc_get_rpa_freq(9)xe_guc_pc_get_rpe_freq(9)xe_guc_pc_get_rpn_freq(9)xe_guc_pc_get_min_freq(9)xe_guc_pc_set_min_freq(9)xe_guc_pc_get_max_freq(9)xe_guc_pc_set_max_freq(9)xe_guc_pc_c_status(9)xe_guc_pc_rc6_residency(9)xe_guc_pc_mc6_residency(9)xe_guc_pc_raise_unslice(9)xe_guc_pc_init_early(9)xe_guc_pc_apply_flush_freq_limit(9)xe_guc_pc_remove_flush_freq_limit(9)xe_guc_pc_restore_stashed_freq(9)xe_guc_pc_start(9)xe_guc_pc_stop(9)xe_guc_pc_fini_hw(9)xe_guc_pc_init(9)xe_guc_pc_print(9)
mwah π thatβs the whole page. source/version vibes: shipped from ./drivers/gpu/drm/xe, dated October 2026, and the page name is xe_guc_pc_get_cur_freq(9). bye bestie, go get that freq π§π
π¦ 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