From: Sanford Rockowitz <rockowitz-9+fK6rGKj7RBDgjK7y7TUQ@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: need guidance re amdgpu i2c
Date: Tue, 13 Sep 2016 06:47:01 -0400 [thread overview]
Message-ID: <57D7D925.4050306@minsoft.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1929 bytes --]
First, apologies in advance if this is not the most appropriate list for
my questions. Redirection appreciated.
I am the author of ddctool <www.ddctool.com>, a utility to manipulate
monitor settings using DDC/CI over I2C.
My understanding is that amdgpu provides /dev/i2c-* devices in the usual
way, so that ddctool should just work without changes. But of course
this needs to be tested.
In this regard I have a number of questions and a request.
Does the i2c interface depend in some way on whether one is running the
AMDGPU-PRO driver?
The most current AMD card that I own in a R9 280, which is a first
generation GCN device. Phoronix suggests that first generation GCN
support is in the works. Will this be soon? If not, would the current
development code for amdgpu be sufficient for me to test the i2c
support? If so, what would I have to do to build and install it?
Or should I just plunk down a few dollars for a relatively inexpensive
R7 260, which I understand is supported by the current amdgpu?
Alternatively, if someone running the amdgpu driver would be willing to
install and test ddctool on their system I'd be most appreciative. The
git repository is here: https://github.com/rockowitz/ddctool, and
there's extensive documentation on the website, www.ddctool.com.
A couple of command line options of note:
"--stats" reports extensive performance statistics, including counts
of i2c retries required
"--ddc" reports DDC protocol data errors
If ddctool installs but does not seem to be working, command "ddctool
environment" may provide some clues.
Finally, the "ddctool interrogate" command fully exercises ddctool and
probes the i2c environment. Depending on permissions, running it as
root may provide additional detail. If you can capture the output and
send it to me that would be most helpful.
Thanks in advance,
Sanford Rockowitz
[-- Attachment #1.2: Type: text/html, Size: 2537 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2016-09-13 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 10:47 Sanford Rockowitz [this message]
[not found] ` <57D7D925.4050306-9+fK6rGKj7RBDgjK7y7TUQ@public.gmane.org>
2016-09-13 16:16 ` need guidance re amdgpu i2c Deucher, Alexander
[not found] ` <e0498ba7-fc4a-4fa3-7362-88c7b88d78bb@inbox.com>
[not found] ` <e0498ba7-fc4a-4fa3-7362-88c7b88d78bb-BoNl9JPmOHUAvxtiuMwx3w@public.gmane.org>
2016-09-13 20:43 ` Sanford Rockowitz
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=57D7D925.4050306@minsoft.com \
--to=rockowitz-9+fk6rgkj7rbdgjk7y7tuq@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 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.