From: C Stout <cstout@chromium.org>
To: dri-devel@lists.freedesktop.org
Cc: cstout <cstout@google.com>
Subject: [PATCH 4/4] Print details in case of a protect fault interrupt
Date: Thu, 18 Feb 2016 16:50:03 -0800 [thread overview]
Message-ID: <1455843003-60379-4-git-send-email-cstout@chromium.org> (raw)
In-Reply-To: <1455843003-60379-1-git-send-email-cstout@chromium.org>
From: cstout <cstout@google.com>
Change-Id: I44f9854e7a7458730d9bfbfeef3361c438e381d2
---
drivers/gpu/drm/msm/adreno/a4xx_gpu.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpu/drm/msm/adreno/a4xx_gpu.c b/drivers/gpu/drm/msm/adreno/a4xx_gpu.c
index 9aab904..496732d 100644
--- a/drivers/gpu/drm/msm/adreno/a4xx_gpu.c
+++ b/drivers/gpu/drm/msm/adreno/a4xx_gpu.c
@@ -357,6 +357,13 @@ static irqreturn_t a4xx_irq(struct msm_gpu *gpu)
status = gpu_read(gpu, REG_A4XX_RBBM_INT_0_STATUS);
DBG("%s: Int status %08x", gpu->name, status);
+ if (status & (1 << A4XX_INT_CP_REG_PROTECT_FAULT)) {
+ uint32_t reg = gpu_read(gpu, REG_A4XX_CP_PROTECT_STATUS);
+ printk("CP | Protected mode error| %s | addr=%x\n",
+ reg & (1 << 24) ? "WRITE" : "READ",
+ (reg & 0xFFFFF) >> 2);
+ }
+
gpu_write(gpu, REG_A4XX_RBBM_INT_CLEAR_CMD, status);
msm_gpu_retire(gpu);
--
2.1.4
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-02-19 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 0:50 [PATCH 1/4] Support for adreno 430 C Stout
2016-02-19 0:50 ` [PATCH 2/4] Add adreno430 power control C Stout
2016-02-22 13:46 ` Emil Velikov
2016-02-22 14:51 ` Rob Clark
2016-02-22 15:28 ` Emil Velikov
2016-02-19 0:50 ` [PATCH 3/4] Get CP_RPTR from register instead of shadow memory C Stout
2016-02-19 0:50 ` C Stout [this message]
2016-02-22 12:48 ` [PATCH 1/4] Support for adreno 430 Emil Velikov
2016-02-22 12:52 ` Emil Velikov
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=1455843003-60379-4-git-send-email-cstout@chromium.org \
--to=cstout@chromium.org \
--cc=cstout@google.com \
--cc=dri-devel@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).