public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chuansheng Liu <chuansheng.liu@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: lucas.demarchi@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register
Date: Thu, 10 Feb 2022 12:50:08 +0200	[thread overview]
Message-ID: <87k0e3807z.fsf@intel.com> (raw)
In-Reply-To: <20220210050501.87795-1-chuansheng.liu@intel.com>

On Thu, 10 Feb 2022, Chuansheng Liu <chuansheng.liu@intel.com> wrote:
> Current DMC_DEBUG3(_MMIO(0x101090)) address is for TGL,
> it is not wrong for DG1. Just like commit 5bcc95ca382e

wrong, not "not wrong".

BR,
Jani.

> ("drm/i915/dg1: Update DMC_DEBUG register"), correct
> this issue for DG1 platform to avoid wrong register
> being read.
>
> BSpec: 49788
>
> Signed-off-by: Chuansheng Liu <chuansheng.liu@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display_debugfs.c | 4 ++--
>  drivers/gpu/drm/i915/i915_reg.h                      | 3 ++-
>  2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> index f4de004d470f..f6c4ad8fce19 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> @@ -474,8 +474,8 @@ static int i915_dmc_info(struct seq_file *m, void *unused)
>  		 * reg for DC3CO debugging and validation,
>  		 * but TGL DMC f/w is using DMC_DEBUG3 reg for DC3CO counter.
>  		 */
> -		seq_printf(m, "DC3CO count: %d\n",
> -			   intel_de_read(dev_priv, DMC_DEBUG3));
> +		seq_printf(m, "DC3CO count: %d\n", intel_de_read(dev_priv, IS_DGFX(dev_priv) ?
> +					DG1_DMC_DEBUG3 : TGL_DMC_DEBUG3));
>  	} else {
>  		dc5_reg = IS_BROXTON(dev_priv) ? BXT_DMC_DC3_DC5_COUNT :
>  						 SKL_DMC_DC3_DC5_COUNT;
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 87c92314ee26..9c215a6df659 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -5632,7 +5632,8 @@
>  #define TGL_DMC_DEBUG_DC6_COUNT	_MMIO(0x101088)
>  #define DG1_DMC_DEBUG_DC5_COUNT	_MMIO(0x134154)
>  
> -#define DMC_DEBUG3		_MMIO(0x101090)
> +#define TGL_DMC_DEBUG3		_MMIO(0x101090)
> +#define DG1_DMC_DEBUG3		_MMIO(0x13415c)
>  
>  /* Display Internal Timeout Register */
>  #define RM_TIMEOUT		_MMIO(0x42060)

-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2022-02-10 10:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  5:05 [Intel-gfx] [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register Chuansheng Liu
2022-02-10  5:27 ` Matt Roper
2022-02-10  5:36   ` Liu, Chuansheng
2022-02-10  5:29 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-02-10  5:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-10  7:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-15  5:15   ` Matt Roper
2022-02-22 17:39     ` Vudum, Lakshminarayana
2022-02-10 10:50 ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-10 16:44 [Intel-gfx] [PATCH] " Anusha Srivatsa
2022-02-10 17:37 ` Tvrtko Ursulin
2022-02-10 18:51 ` Matt Roper
2022-02-10 19:15   ` Srivatsa, Anusha

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=87k0e3807z.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chuansheng.liu@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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