From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: sunil.kamath@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Use num_scalers instead of SKL_NUM_SCALERS in debugfs
Date: Mon, 21 Nov 2016 13:46:02 +0200 [thread overview]
Message-ID: <1479728762.3435.10.camel@gmail.com> (raw)
In-Reply-To: <1479664226-22307-1-git-send-email-sunil.kamath@intel.com>
On Sun, 2016-11-20 at 23:20 +0530, sunil.kamath@intel.com wrote:
> From: "A.Sunil Kamath" <sunil.kamath@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.kamath@intel.com>
Reviewed-by: Ander Conselvan de Oliveira <conselvan2@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
prev parent reply other threads:[~2016-11-21 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 17:50 [PATCH] drm/i915: Use num_scalers instead of SKL_NUM_SCALERS in debugfs sunil.kamath
2016-11-20 18:16 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-11-21 11:59 ` Ander Conselvan De Oliveira
2016-11-21 11:46 ` Ander Conselvan De Oliveira [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1479728762.3435.10.camel@gmail.com \
--to=conselvan2@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sunil.kamath@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.