All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: DRI Devel <dri-devel@lists.freedesktop.org>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
	jacob.jun.pan@linux.intel.com, arjan@linux.intel.com
Subject: Re: [RFC] Unified DRM GPU frequency knobs
Date: Sun, 9 Sep 2012 12:59:20 -0700	[thread overview]
Message-ID: <20120909125920.5816b189@bwidawsk.net> (raw)
In-Reply-To: <20120909124255.288864aa@bwidawsk.net>

On Sun, 9 Sep 2012 12:42:55 -0700
Ben Widawsky <ben@bwidawsk.net> wrote:

> On the Intel driver we've developed and reviewed some patches which
> enable GPU frequency settings in sysfs. Similar interfaces have
> existed for some time in our debugfs, but now we're getting interest
> from users like PowerTOP and have decided to formalize it. Most
> likely other DRM drivers have similar features; and perhaps similar
> proposals have gone out in the past.
> 
> Boiling down what we've exposed in our patches:
> read current GPU frequency
> read/write min frequency
> read/write max frequency
> read HW support lowest frequency (we call this RPn)
> read HW supported highest frequency (we call this RP0)
> read HW recommended low frequnecy (we call this RP1)
> 
> If no interest is perceived we will move forward with these as Intel
> only sysfs interfaces.
> 
> The Intel specific patches which are ready to go are here:
> http://lists.freedesktop.org/archives/intel-gfx/2012-September/020342.html
> 
> Thanks.
> 

I was called out for not being clear. I'm asking if there
is interest in making unified knobs in DRM as opposed to driver specific
knobs. Is that even a good idea, and/or make sense to do?



-- 
Ben Widawsky, Intel Open Source Technology Center

      reply	other threads:[~2012-09-09 19:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09 19:42 [RFC] Unified DRM GPU frequency knobs Ben Widawsky
2012-09-09 19:59 ` Ben Widawsky [this message]

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=20120909125920.5816b189@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=arjan@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jacob.jun.pan@linux.intel.com \
    /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.