intel_guc_slpc_get_max_freq(9)
π
intel_guc_slpc_get_max_freq(9) π
okay bestie, this is the page from the Kernel API Manual for intel_guc_slpc_get_max_freq(9) β yes, the manual name is folded in right here so we can keep it cute β¨.
πΈ NAME πΈ
intel_guc_slpc_get_max_freqβ Get max frequency limit for SLPC. periodt π
β¨ SYNOPSIS β¨
int intel_guc_slpc_get_max_freq (struct intel_guc_slpc *slpc , u32 *val
);
π ARGUMENTS π
slpcβ pointer tointel_guc_slpcπ.valβ pointer tovalwhich will hold max frequency (MHz) π.
π¦ DESCRIPTION π¦
Calling this bad boy invokes the GuC SLPC action to read the max frequency limit for unslice. It's literally giving "ask GuC what the max frequency limit is for unslice" energy, and honestly? iconic π₯.
π RETURN π
0 on success, non-zero error code on failure π. That's the whole vibe check: clean 0 means slay, non-zero means something went nope.
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.c SLPC - Dynamic Frequency management(9)intel_guc_slpc_set_max_freq(9)intel_guc_slpc_set_min_freq(9)intel_guc_slpc_get_min_freq(9)
mwah π this page comes from source/version ./drivers/gpu/drm/i915/gt/uc and is dated October 2026 β title intel_guc_slpc_get_max_freq(9), out β¨π«Ά
π¦ 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