From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Ben Widawsky <ben@bwidawsk.net>,
f@chad-versace.us, Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
Ben Widawsky <benjamin.widawsky@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH v4] drm/i915: rc6 in sysfs
Date: Wed, 11 Apr 2012 11:51:01 +0200 [thread overview]
Message-ID: <20120411095101.GA4296@phenom.ffwll.local> (raw)
In-Reply-To: <1334132085_361270@CP5-2952>
On Wed, Apr 11, 2012 at 09:14:43AM +0100, Chris Wilson wrote:
> On Tue, 10 Apr 2012 21:17:01 -0700, Ben Widawsky <ben@bwidawsk.net> 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 drm core). 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 rc6 modes enabled (as a hex mask):
> > cat /sys/class/drm/card0/power/rc6_enable
> >
> > displays #ms GPU has been in rc6 since boot:
> > cat /sys/class/drm/card0/power/rc6_residency_ms
> >
> > displays #ms GPU has been in deep rc6 since boot:
> > cat /sys/class/drm/card0/power/rc6p_residency_ms
> >
> > displays #ms GPU has been in deepest rc6 since boot:
> > cat /sys/class/drm/card0/power/rc6pp_residency_ms
> >
> > 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 can only guess at the
> > reason reason for this. Those writing tools that utilize this value need
> > to be careful and probably want to scrutinize the value very carefully.
> >
> > v2: use common rc6 residency units to milliseconds for the other RC6 types
> >
> > v3: don't create sysfs files for GEN <= 5
> > add a rc6_enable to show a mask of enabled rc6 types
> > use unmerge instead of remove for sysfs group
> > squash intel_enable_rc6() extraction into this patch
> >
> > v4: rename sysfs files (Chris)
> >
> > CC: Chris Wilson <chris@chris-wilson.co.uk>
> > CC: Daniel Vetter <daniel.vetter@ffwll.ch>f
> > CC: Arjan van de Ven <arjan@linux.intel.com>
> > Signed-off-by: Ben Widawsky <benjamin.widawsky@intel.com>
>
> So the only downside to using the pre-existing power group is that we do
> not get the interface if power-management is compiled out of the kernel,
> which I suppose is appropriate.
>
> I'm down to just bikeshedding over useless lines of code which do not
> even add visual clarity...
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-04-11 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 4:17 [PATCH v4] drm/i915: rc6 in sysfs Ben Widawsky
2012-04-11 8:14 ` Chris Wilson
2012-04-11 9:51 ` Daniel Vetter [this message]
2012-04-11 22:10 ` Chris Wilson
2012-04-11 22:37 ` Daniel Vetter
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=20120411095101.GA4296@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=arjan@linux.intel.com \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=f@chad-versace.us \
--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 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.