On Thu, Jan 29, 2026 at 10:41:54PM +0530, Ankit Nautiyal wrote:
> From: Chaitanya Kumar Borah <[email protected]>
> 
> Add upper limit check for pixel clock for WCL.
> 
> For prior platforms though the bspec mentions the dotclock limits, however
> these are intentionally not enforced to avoid regressions, unless real
> issues are observed.
> 
> BSpec: 49199, 68912
> Signed-off-by: Chaitanya Kumar Borah <[email protected]>
> Signed-off-by: Ankit Nautiyal <[email protected]>

Reviewed-by: Imre Deak <[email protected]>

> ---
>  drivers/gpu/drm/i915/display/intel_display.c | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c 
> b/drivers/gpu/drm/i915/display/intel_display.c
> index 9cfeb5530fd8..bd4219467e0e 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -8006,8 +8006,16 @@ int intel_max_uncompressed_dotclock(struct 
> intel_display *display)
>       int max_dotclock = display->cdclk.max_dotclk_freq;
>       int limit = max_dotclock;
>  
> -     if (DISPLAY_VER(display) >= 30)
> +     if (DISPLAY_VERx100(display) == 3002)
> +             limit = 937500;
> +     else if (DISPLAY_VER(display) >= 30)
>               limit = 1350000;
> +     /*
> +      * Note: For other platforms though there are limits given
> +      * in the Bspec, however the limit is intentionally not
> +      * enforced to avoid regressions, unless real issues are
> +      * observed.
> +      */
>  
>       return min(max_dotclock, limit);
>  }
> -- 
> 2.45.2
> 

Reply via email to