From: "Siluvery, Arun" <arun.siluvery@linux.intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: miku@iki.fi
Subject: Re: [PATCH 4/4] drm/i915: Check workaround status on dfs read time
Date: Mon, 13 Oct 2014 16:22:16 +0100 [thread overview]
Message-ID: <543BEE28.6060505@linux.intel.com> (raw)
In-Reply-To: <1412691687-12466-4-git-send-email-mika.kuoppala@intel.com>
On 07/10/2014 15:21, Mika Kuoppala wrote:
> As the workaround list has the value as initialization time
> constant, we can do the simple checking on the go without
> negleting igt.
>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 87482f8..dbd5dc5 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -2659,16 +2659,16 @@ static int i915_wa_registers(struct seq_file *m, void *unused)
>
> seq_printf(m, "Workarounds applied: %d\n", dev_priv->workarounds.count);
> for (i = 0; i < dev_priv->workarounds.count; ++i) {
> - u32 addr, mask;
> + u32 addr, mask, value, read;
> + bool ok;
>
> addr = dev_priv->workarounds.reg[i].addr;
> mask = dev_priv->workarounds.reg[i].mask;
> - dev_priv->workarounds.reg[i].value = I915_READ(addr) | mask;
> - if (dev_priv->workarounds.reg[i].addr)
> - seq_printf(m, "0x%X: 0x%08X, mask: 0x%08X\n",
> - dev_priv->workarounds.reg[i].addr,
> - dev_priv->workarounds.reg[i].value,
> - dev_priv->workarounds.reg[i].mask);
> + value = dev_priv->workarounds.reg[i].value;
> + read = I915_READ(addr);
> + ok = (value & mask) == (read & mask);
> + seq_printf(m, "0x%X: 0x%08X, mask: 0x%08X, read: 0x%08x, status: %s\n",
> + addr, value, mask, read, ok ? "OK" : "FAIL");
> }
>
> intel_runtime_pm_put(dev_priv);
>
Reviewed-by: Arun Siluvery <arun.siluvery@linux.intel.com>
regards
Arun
prev parent reply other threads:[~2014-10-13 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 14:21 [PATCH 1/4] drm/i915: Restore default render context after hw state reset Mika Kuoppala
2014-10-07 14:21 ` [PATCH 2/4] drm/i915: Reinitialize default context after resume Mika Kuoppala
2014-10-07 15:06 ` Chris Wilson
2014-10-07 14:21 ` [PATCH 3/4] drm/i915: Build workaround list in ring initialization Mika Kuoppala
2014-10-13 15:21 ` Siluvery, Arun
2014-10-20 16:13 ` Siluvery, Arun
2014-10-21 12:52 ` Daniel Vetter
2014-10-21 15:54 ` Mika Kuoppala
2014-10-07 14:21 ` [PATCH 4/4] drm/i915: Check workaround status on dfs read time Mika Kuoppala
2014-10-13 15:22 ` Siluvery, Arun [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=543BEE28.6060505@linux.intel.com \
--to=arun.siluvery@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
--cc=miku@iki.fi \
/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