From: Tom St Denis <tstdenis82-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: GPR read support via debugfs (v2)
Date: Tue, 6 Dec 2016 09:50:11 -0500 [thread overview]
Message-ID: <20161206145014.9140-1-tom.stdenis@amd.com> (raw)
These patches introduce debugfs access to read GPRs (SGPRs for now).
(v2): Fixes white space, addressing is in dwords not bytes, and removes
the buggy sanity checking.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2016-12-06 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 14:50 Tom St Denis [this message]
[not found] ` <20161206145014.9140-1-tom.stdenis-5C7GfCeVMHo@public.gmane.org>
2016-12-06 14:50 ` [PATCH 1/3] drm/amd/amdgpu: Add debugfs support for reading GPRs (v2) Tom St Denis
2016-12-06 14:50 ` [PATCH 2/3] drm/amd/amdgpu: Add gpr reading for GFX v6 Tom St Denis
2016-12-06 14:50 ` [PATCH 3/3] drm/amd/amdgpu: Add gpr reading for GFX v7 Tom St Denis
2016-12-06 22:15 ` GPR read support via debugfs (v2) Edward O'Callaghan
[not found] ` <b0979deb-7d97-f81f-65af-3a0800d55e4b-dczkZgxz+BNUPWh3PAxdjQ@public.gmane.org>
2016-12-07 17:05 ` StDenis, Tom
[not found] ` <CY4PR12MB1768F2C7EF86AE04BB957AEAF7850-rpdhrqHFk06yjjPBNVDk/QdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-12-07 17:32 ` Alex Deucher
[not found] ` <CADnq5_OJJFGDLt405YdQN3k6O5jbM_t0miDo=ZenMp9jG9QjcA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-07 17:49 ` StDenis, Tom
[not found] ` <CY4PR12MB1768C0C95CA7F8A50E07C28AF7850-rpdhrqHFk06yjjPBNVDk/QdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-12-07 17:59 ` Marek Olšák
[not found] ` <CAAxE2A6d6XuB8wSG2foFEsVVgJcZh5fVXYKRwsRQA=ao6q5f4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-07 18:46 ` Christian König
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=20161206145014.9140-1-tom.stdenis@amd.com \
--to=tstdenis82-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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