Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Vinod Govindapillai <vinod.govindapillai@intel.com>
Cc: intel-gfx@lists.freedesktop.org, stanislav.lisovskiy@intel.com,
	ville.syrjala@intel.com, jani.saarinen@intel.com
Subject: Re: [PATCH v10 1/6] drm/i915/display: Add meaningful traces for QGV point info error handling
Date: Fri, 19 Apr 2024 20:11:46 +0300	[thread overview]
Message-ID: <ZiKl0i53spdT8LzY@intel.com> (raw)
In-Reply-To: <20240405113533.338553-2-vinod.govindapillai@intel.com>

On Fri, Apr 05, 2024 at 02:35:28PM +0300, Vinod Govindapillai wrote:
> From: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> 
> For debug purposes we need those - error path won't flood the log,
> however there has been already numerous cases, when due to lack
> of debugs, we couldn't immediately tell what was the problem on
> customer machine, which slowed down the investigation, requiring
> to get access to target device and adding those traces manually.
> 
> v2: - Make the debug more generic and move it to intel_dram_detect
>       (Gustavo Sousa)
> v3: - Use %u for unsigned variable in debug prints (Gustavo)
> 
> Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_bw.c | 4 +++-
>  drivers/gpu/drm/i915/soc/intel_dram.c   | 2 ++
>  2 files changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
> index 7f2a50b4f494..77886cc21211 100644
> --- a/drivers/gpu/drm/i915/display/intel_bw.c
> +++ b/drivers/gpu/drm/i915/display/intel_bw.c
> @@ -290,8 +290,10 @@ static int icl_get_qgv_points(struct drm_i915_private *dev_priv,
>  		struct intel_qgv_point *sp = &qi->points[i];
>  
>  		ret = intel_read_qgv_point_info(dev_priv, sp, i);
> -		if (ret)
> +		if (ret) {
> +			drm_dbg_kms(&dev_priv->drm, "Could not read QGV %d info\n", i);

s/QGV/QGV point/ would be more clear.

>  			return ret;
> +		}
>  
>  		drm_dbg_kms(&dev_priv->drm,
>  			    "QGV %d: DCLK=%d tRP=%d tRDPRE=%d tRAS=%d tRCD=%d tRC=%d\n",
> diff --git a/drivers/gpu/drm/i915/soc/intel_dram.c b/drivers/gpu/drm/i915/soc/intel_dram.c
> index 15492b69f698..e3287f1de774 100644
> --- a/drivers/gpu/drm/i915/soc/intel_dram.c
> +++ b/drivers/gpu/drm/i915/soc/intel_dram.c
> @@ -681,6 +681,8 @@ void intel_dram_detect(struct drm_i915_private *i915)
>  	if (ret)
>  		return;
>  
> +	drm_dbg_kms(&i915->drm, "Num qgv points %u\n", dram_info->num_qgv_points);
> +

This doesn't seem to belong here.

>  	drm_dbg_kms(&i915->drm, "DRAM channels: %u\n", dram_info->num_channels);
>  
>  	drm_dbg_kms(&i915->drm, "Watermark level 0 adjustment needed: %s\n",
> -- 
> 2.34.1

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-04-19 17:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 11:35 [PATCH v10 0/6] QGV/SAGV related fixes Vinod Govindapillai
2024-04-05 11:35 ` [PATCH v10 1/6] drm/i915/display: Add meaningful traces for QGV point info error handling Vinod Govindapillai
2024-04-19 17:11   ` Ville Syrjälä [this message]
2024-04-05 11:35 ` [PATCH v10 2/6] drm/i915/display: Extract code required to calculate max qgv/psf gv point Vinod Govindapillai
2024-04-08  8:32   ` Lisovskiy, Stanislav
2024-04-08 10:25     ` Govindapillai, Vinod
2024-04-05 11:35 ` [PATCH v10 3/6] drm/i915/display: extract code to prepare qgv points mask Vinod Govindapillai
2024-04-05 11:35 ` [PATCH v10 4/6] drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation Vinod Govindapillai
2024-04-05 11:35 ` [PATCH v10 5/6] drm/i915/display: handle systems with duplicate psf gv points Vinod Govindapillai
2024-04-08  8:29   ` Lisovskiy, Stanislav
2024-04-08 10:18     ` Govindapillai, Vinod
2024-04-05 11:35 ` [PATCH v10 6/6] drm/i915/display: force qgv check after the hw state readout Vinod Govindapillai
2024-04-19 17:19   ` Ville Syrjälä
2024-04-23  7:40     ` Govindapillai, Vinod
2024-04-23  7:46       ` Govindapillai, Vinod
2024-04-22  7:54   ` Lisovskiy, Stanislav
2024-04-05 12:24 ` ✗ Fi.CI.SPARSE: warning for QGV/SAGV related fixes (rev10) Patchwork
2024-04-05 12:40 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-06  5:02 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-06  7:38 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-19  8:42 ` [PATCH v10 0/6] QGV/SAGV related fixes Hogander, Jouni
2024-04-19 13:32   ` Govindapillai, Vinod

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=ZiKl0i53spdT8LzY@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=stanislav.lisovskiy@intel.com \
    --cc=ville.syrjala@intel.com \
    --cc=vinod.govindapillai@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