Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org,
	Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH 3/3] drm/i915: rc6 in sysfs
Date: Wed, 28 Mar 2012 17:31:25 -0700	[thread overview]
Message-ID: <20120328173125.250ec06a@bwidawsk.net> (raw)
In-Reply-To: <20120325121556.GB5909@phenom.ffwll.local>

On Sun, 25 Mar 2012 14:15:56 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:

> On Sat, Mar 24, 2012 at 07:09:46PM -0700, Ben Widawsky wrote:
> > Merge rc6 information into the power group for our device. Until
> > now the i915 driver has not had any sysfs entries (aside from the
> > connector stuff enabled by libdrm). Since it seems like we're
> > likely to have more in the future I created a new file for sysfs
> > stubs, as well as the rc6 sysfs functions which don't really belong
> > elsewhere (perhaps i915_suspend, but most of the stuff is in
> > intel_display,c).
> > 
> > displays #ms GPU has been in rc6 since boot:
> > cat /sys/class/drm/card0/power/rc6
> > 
> > displays #ms GPU has been in deep rc6 since boot:
> > cat /sys/class/drm/card0/power/rc6p
> > 
> > displays #ms GPU has been in deepest rc6 since boot:
> > cat /sys/class/drm/card0/power/rc6pp
> > 
> > Important note: I've seen on SNB that even when RC6 is *not*
> > enabled the rc6 register seems to have a random value in it. I
> > cannot explain a reason for this. Those writing tools that utilize
> > this value need to be careful and probably want to scrutinize the
> > value very carefully.
> > 
> > Please see intel-gpu-tools patches for sample code.
> > 
> > CC: Arjan van de Ven <arjan@linux.intel.com>
> > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> 
> I like this (with the cleanups you've mentioned). While you dig
> around in sysfs, can I volunteer you to add another patch to create
> an official interface for i915_max_freq? Maybe call it
> max_gpu_freq_MHz (if MHz is an acceptable unit for sysfs files). We
> have a bug report which might get partially happy with this (there
> seem to be other issues):
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=41392a
> 
> Cheers, Daniel
> 

Yes. From looking at cpureq, it seems MHz is not standard. Simply
writing the frequency as a number in the [m|b]illions is the way to go.

I'll get on this once I get an ack from you that you pick up the later
versions of my sysfs stuff. 

  reply	other threads:[~2012-03-29  0:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25  2:09 [PATCH 1/3] drm/i915: add rc6 residency times to debugfs Ben Widawsky
2012-03-25  2:09 ` [PATCH 2/3] drm/i915: extract intel_enable_rc6() Ben Widawsky
2012-03-25 12:10   ` Daniel Vetter
2012-03-29  0:30     ` Ben Widawsky
2012-03-25  2:09 ` [PATCH 3/3] drm/i915: rc6 in sysfs Ben Widawsky
2012-03-25  2:14   ` Ben Widawsky
2012-03-25 12:15   ` Daniel Vetter
2012-03-29  0:31     ` Ben Widawsky [this message]
2012-03-25  2:09 ` [PATCH 1/2] build: make sure we have asprintf Ben Widawsky
2012-03-25  2:09 ` [PATCH 2/2] tests: rc6 residency test Ben Widawsky
2012-03-25 12:21   ` Daniel Vetter
2012-03-25  2:22 ` [PATCH 1/3] drm/i915: add rc6 residency times to debugfs Ben Widawsky

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=20120328173125.250ec06a@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=arjan@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox