From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon/kms: add support for internal thermal sensors
Date: Tue, 1 Jun 2010 21:42:31 +0100 [thread overview]
Message-ID: <20100601204231.GB16575@srcf.ucam.org> (raw)
In-Reply-To: <1275424301-7507-1-git-send-email-alexdeucher@gmail.com>
On Tue, Jun 01, 2010 at 04:31:41PM -0400, Alex Deucher wrote:
> rv6xx/rv7xx/evergreen families supported; older asics did
> not have an internal thermal sensor. Exposed via sysfs
> gpu_temp attribute.
This really should be done via the standard hwmon naming - some of the
sensor tools depend on it. If there's only one sensor per GPU
"temp1_input" is correct, with a "name" attribute indicating which card
provides it. Also, make sure that you're exporting in millidegrees
rather than degrees.
> Note also, that most laptops use an oem specific ACPI solution for
> GPU thermal information rather than using the internal thermal
> sensor directly.
Is there any mechanism for determining which ACPI thermal zone is
associated with the GPU, or is this something that's hardcoded into the
drivers?
> + /* where's the best place to put this? */
> + sysfs_create_group(&rdev->dev->kobj, &evergreen_hwmon_attrgroup);
They should be under the hwmon device.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-06-01 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 20:31 [PATCH] drm/radeon/kms: add support for internal thermal sensors Alex Deucher
2010-06-01 20:42 ` Matthew Garrett [this message]
2010-06-01 21:41 ` Alex Deucher
2010-06-01 21:45 ` Matthew Garrett
2010-06-01 22:52 ` [PATCH] drm/radeon/kms: add support for internal thermal sensors (v2) Alex Deucher
2010-06-02 11:55 ` Julien Cristau
2010-06-02 15:51 ` Alex Deucher
2010-06-02 16:59 ` [PATCH] drm/radeon/kms: add support for internal thermal sensors (v3) Alex Deucher
2010-06-02 21:46 ` Frieder Ferlemann
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=20100601204231.GB16575@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alexdeucher@gmail.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 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.