From: Lauri Kasanen <cand@gmx.com>
To: "Christian König" <deathsimple@vodafone.de>
Cc: cand@gmx.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] radeon: Make PM info available to all, not just debug users
Date: Mon, 4 Jun 2012 19:29:02 +0300 [thread overview]
Message-ID: <20120604192902.149fd73d.cand@gmx.com> (raw)
In-Reply-To: <4FCCDFC2.6060602@vodafone.de>
On Mon, 04 Jun 2012 18:18:10 +0200
Christian König <deathsimple@vodafone.de> wrote:
> > My experience is that things that are true today for GPU, are not
> > tomorrow. Yes there will still be clock/voltage, but there could be
> > new complete different things, like shutting down block.
> >
> > I am not even mentioning things like complex value range dependency
> > btw things (for instance if a domain as clock/voltage in certain range
> > than some other domain can only have clock in a restricted range
> > value).
> >
> > While i agree that sysfs looks easy for user to play with, i believe
> > that gui is what you really after and afaik closed source driver all
> > expose a gui for their power management. Using ioctl allow better
> > overall control, like atomic setting of several domain ...
>
> Yeah, I think Jerome is right here.
>
> The internals like different voltage areas, dependencies of clocks,
> possible powered down chip areas, etc are very complex and actually
> completely unteresting to the end user. Also the general direction of
> AMD hardware is going to a complete self containing system, e.g. the
> chip is handling mostly everything on its own.
>
> I agree that this is better done in a hardware dependent ioctl and then
> abstracted in userspace instead of pushing the whole abstraction into
> the kernel.
Hi
As long as the info is made available better than it is currently, I'm all for it.
Though with the direction of ioctl and folks, it is deep outside my expertise. With a deep solution like that someone who knows the area well would need to do it.
- Lauri
next prev parent reply other threads:[~2012-06-04 16:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 16:08 [PATCH] radeon: Make PM info available to all, not just debug users Lauri Kasanen
2012-06-03 10:54 ` Christian König
2012-06-04 8:44 ` Lauri Kasanen
2012-06-04 11:30 ` Christian König
2012-06-04 12:30 ` Alex Deucher
2012-06-04 12:40 ` Martin Peres
2012-06-04 14:31 ` Jerome Glisse
2012-06-04 15:02 ` Martin Peres
2012-06-04 15:18 ` Jerome Glisse
2012-06-04 16:18 ` Christian König
2012-06-04 16:29 ` Lauri Kasanen [this message]
2012-06-04 17:05 ` Jerome Glisse
2012-06-05 10:11 ` Lauri Kasanen
2012-06-04 17:01 ` Martin Peres
2012-06-04 17:19 ` Jerome Glisse
2012-06-04 17:54 ` Martin Peres
2012-06-04 18:18 ` Jerome Glisse
2012-06-04 18:29 ` Jerome Glisse
2012-06-04 20:31 ` Martin Peres
2012-06-04 19:54 ` Daniel Vetter
2012-06-04 20:34 ` Martin Peres
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=20120604192902.149fd73d.cand@gmx.com \
--to=cand@gmx.com \
--cc=deathsimple@vodafone.de \
--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.