public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Output scaler related pipe config debug in a single line
Date: Wed, 13 May 2015 17:26:17 +0100	[thread overview]
Message-ID: <20150513162616.GC10669@strange.amr.corp.intel.com> (raw)
In-Reply-To: <1431532268-4363-2-git-send-email-tvrtko.ursulin@linux.intel.com>

On Wed, May 13, 2015 at 04:51:08PM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> 
> Just so it is grouped logically in line with other data and makes a
> rather verbose output a bit shorter.
> 
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Chandra Konduru <chandra.konduru@intel.com>

Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>

-- 
Damien

> ---
>  drivers/gpu/drm/i915/intel_display.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index b3ed8a0..92f3324 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -11404,9 +11404,10 @@ static void intel_dump_pipe_config(struct intel_crtc *crtc,
>  	DRM_DEBUG_KMS("port clock: %d\n", pipe_config->port_clock);
>  	DRM_DEBUG_KMS("pipe src size: %dx%d\n",
>  		      pipe_config->pipe_src_w, pipe_config->pipe_src_h);
> -	DRM_DEBUG_KMS("num_scalers: %d\n", crtc->num_scalers);
> -	DRM_DEBUG_KMS("scaler_users: 0x%x\n", pipe_config->scaler_state.scaler_users);
> -	DRM_DEBUG_KMS("scaler id: %d\n", pipe_config->scaler_state.scaler_id);
> +	DRM_DEBUG_KMS("num_scalers: %d, scaler_users: 0x%x, scaler_id: %d\n",
> +		      crtc->num_scalers,
> +		      pipe_config->scaler_state.scaler_users,
> +		      pipe_config->scaler_state.scaler_id);
>  	DRM_DEBUG_KMS("gmch pfit: control: 0x%08x, ratios: 0x%08x, lvds border: 0x%08x\n",
>  		      pipe_config->gmch_pfit.control,
>  		      pipe_config->gmch_pfit.pgm_ratios,
> -- 
> 2.4.0
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-05-13 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 15:51 [PATCH 1/2] drm/i915: Dump some DPLL fields in pipe config debug Tvrtko Ursulin
2015-05-13 15:51 ` [PATCH 2/2] drm/i915: Output scaler related pipe config debug in a single line Tvrtko Ursulin
2015-05-13 16:26   ` Damien Lespiau [this message]
2015-05-15 13:48   ` shuang.he
2015-05-18  5:27   ` Konduru, Chandra
2015-05-18  7:58     ` Daniel Vetter
2015-05-13 16:41 ` [PATCH 1/2] drm/i915: Dump some DPLL fields in pipe config debug Damien Lespiau
2015-05-18  7:57   ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2015-05-14 12:38 Tvrtko Ursulin
2015-05-14 12:38 ` [PATCH 2/2] drm/i915: Output scaler related pipe config debug in a single line Tvrtko Ursulin
2015-05-15 15:50   ` shuang.he

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=20150513162616.GC10669@strange.amr.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox