On Sun, 2016-11-20 at 23:20 +0530, sunil.kam...@intel.com wrote:
> From: "A.Sunil Kamath" <sunil.kam...@intel.com>
> 
> Better to use num_scaler itself while printing scaler_info.
> This fixes a bug of printing information for the missing
> second scaler on pipe C for SKL platform.
> 
> Signed-off-by: A.Sunil Kamath <sunil.kam...@intel.com>

Reviewed-by: Ander Conselvan de Oliveira <conselv...@gmail.com>

> ---
>  drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c
> b/drivers/gpu/drm/i915/i915_debugfs.c
> index 1cc971c..6c39881 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -3081,7 +3081,7 @@ static void intel_scaler_info(struct seq_file *m, struct
> intel_crtc *intel_crtc)
>                          pipe_config->scaler_state.scaler_users,
>                          pipe_config->scaler_state.scaler_id);
>  
> -             for (i = 0; i < SKL_NUM_SCALERS; i++) {
> +             for (i = 0; i < num_scalers; i++) {
>                       struct intel_scaler *sc =
>                                       &pipe_config-
> >scaler_state.scalers[i];
>  
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to