From: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register
Date: Thu, 10 Feb 2022 19:15:17 +0000 [thread overview]
Message-ID: <22a25f9320d74e0190fc966feebc4ce9@intel.com> (raw)
In-Reply-To: <YgVemUgixMuqZEMU@mdroper-desk1.amr.corp.intel.com>
> -----Original Message-----
> From: Roper, Matthew D <matthew.d.roper@intel.com>
> Sent: Thursday, February 10, 2022 10:51 AM
> To: Srivatsa, Anusha <anusha.srivatsa@intel.com>
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register
>
> On Thu, Feb 10, 2022 at 08:44:30AM -0800, Anusha Srivatsa wrote:
> > DMC_DEBUGU3 changes from DG1+
>
> This looks to be the same thing as the patch that Chuansheng Liu sent:
>
> https://patchwork.freedesktop.org/patch/473272/?series=99942&rev=1
Yes it is :-/ He sent the patch before mine. So this is void now.
Anusha
>
> Matt
>
> >
> > Bspec: 49788
> > Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_display_debugfs.c | 6 ++++--
> > drivers/gpu/drm/i915/i915_reg.h | 1 +
> > 2 files changed, 5 insertions(+), 2 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..87fc4b9b7b93 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> > @@ -474,8 +474,10 @@ 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));
> > + if (IS_DGFX(dev_priv))
> > + seq_printf(m, "DC3CO count: %d\n",
> intel_de_read(dev_priv, DG1_DMC_DEBUG3));
> > + else
> > + seq_printf(m, "DC3CO count: %d\n",
> intel_de_read(dev_priv,
> > +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..802962e3977c
> > 100644
> > --- a/drivers/gpu/drm/i915/i915_reg.h
> > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > @@ -5633,6 +5633,7 @@
> > #define DG1_DMC_DEBUG_DC5_COUNT _MMIO(0x134154)
> >
> > #define DMC_DEBUG3 _MMIO(0x101090)
> > +#define DG1_DMC_DEBUG3 _MMIO(0x13415C)
> >
> > /* Display Internal Timeout Register */
> > #define RM_TIMEOUT _MMIO(0x42060)
> > --
> > 2.25.1
> >
>
> --
> Matt Roper
> Graphics Software Engineer
> VTT-OSGC Platform Enablement
> Intel Corporation
> (916) 356-2795
next prev parent reply other threads:[~2022-02-10 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 16:44 [Intel-gfx] [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register Anusha Srivatsa
2022-02-10 17:37 ` Tvrtko Ursulin
2022-02-10 18:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/dg1: Update DMC_DEBUG3 register (rev2) Patchwork
2022-02-10 18:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-10 18:51 ` [Intel-gfx] [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register Matt Roper
2022-02-10 19:15 ` Srivatsa, Anusha [this message]
2022-02-10 21:44 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg1: Update DMC_DEBUG3 register (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
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 10:50 ` Jani Nikula
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=22a25f9320d74e0190fc966feebc4ce9@intel.com \
--to=anusha.srivatsa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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.