From: deepak.s@intel.com
To: intel-gfx@lists.freedesktop.org
Cc: Deepak S <deepak.s@intel.com>
Subject: [PATCH 0/3] drm/i915: Split VLV forcewake routines.
Date: Sat, 23 Nov 2013 14:55:41 +0530 [thread overview]
Message-ID: <1385198744-9333-1-git-send-email-deepak.s@intel.com> (raw)
From: Deepak S <deepak.s@intel.com>
Valleyview has power wells MEDIA & RENDER and by spliting
vlv force wake routines and individually controling Media/Render well,
We have seen power savings in the lower sub-1W range on different
workloads, e.g. glbenchmark, media playback
Deepak S (3):
drm/i915: Add power well arguments to force wake routines.
drm/i915/vlv: Valleyview support for forcewake Individual power wells.
drm/i915: Enabling DebugFS for valleyview forcewake counts
drivers/gpu/drm/i915/i915_debugfs.c | 24 ++--
drivers/gpu/drm/i915/i915_drv.h | 32 ++++-
drivers/gpu/drm/i915/intel_display.c | 4 +-
drivers/gpu/drm/i915/intel_pm.c | 22 ++--
drivers/gpu/drm/i915/intel_ringbuffer.c | 14 ++-
drivers/gpu/drm/i915/intel_uncore.c | 217 +++++++++++++++++++++++++-------
6 files changed, 245 insertions(+), 68 deletions(-)
--
1.8.4.2
next reply other threads:[~2013-11-23 9:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 9:25 deepak.s [this message]
2013-11-23 9:25 ` [PATCH 1/3] drm/i915: Add power well arguments to force wake routines deepak.s
2013-11-25 16:29 ` Jesse Barnes
2013-11-23 9:25 ` [PATCH 2/3] drm/i915/vlv: Valleyview support for forcewake Individual power wells deepak.s
2013-11-25 14:48 ` Chris Wilson
2013-11-26 10:10 ` S, Deepak
2013-11-25 16:36 ` Jesse Barnes
2013-11-23 9:25 ` [PATCH 3/3] drm/i915: Enabling DebugFS for valleyview forcewake counts deepak.s
2013-11-25 16:38 ` Jesse Barnes
2013-11-26 10:12 ` S, Deepak
2013-11-27 15:59 ` Daniel Vetter
2013-11-27 16:30 ` S, Deepak
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=1385198744-9333-1-git-send-email-deepak.s@intel.com \
--to=deepak.s@intel.com \
--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