From: deepak.s@intel.com
To: intel-gfx@lists.freedesktop.org
Cc: Deepak S <deepak.s@intel.com>
Subject: [PATCH 0/4] Fixes for vlv turbo.
Date: Sun, 8 Dec 2013 14:16:42 +0530 [thread overview]
Message-ID: <1386492406-24716-1-git-send-email-deepak.s@intel.com> (raw)
From: Deepak S <deepak.s@intel.com>
This patch includes
1. update current freq properly before requesting new freq.
2. set min delay to rpe delay (Efficient frequency) for better performace.
3. Disable/Enable PM Intrrupts based on the current freq.
4. WA to fix Voltage is not getting dropped to Vmin when Gfx is power gated
Deepak S (4):
drm/i915: update current freq properly before requesting new freq.
drm/i915: set min delay to rpe delay (Efficient frequency) for better
performace.
drm/i915: Disable/Enable PM Intrrupts based on the current freq.
drm/i915: WA to fix Voltage is not getting dropped to Vmin when Gfx is
power gated.
drivers/gpu/drm/i915/i915_drv.h | 4 ++
drivers/gpu/drm/i915/i915_irq.c | 39 +++++++++++++-
drivers/gpu/drm/i915/i915_reg.h | 4 ++
drivers/gpu/drm/i915/intel_pm.c | 114 +++++++++++++++++++++++++++++++++++++++-
4 files changed, 157 insertions(+), 4 deletions(-)
--
1.8.4.2
next reply other threads:[~2013-12-08 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 8:46 deepak.s [this message]
2013-12-08 8:46 ` [PATCH 1/4] drm/i915: update current freq properly before requesting new freq deepak.s
2013-12-09 10:03 ` Ville Syrjälä
2013-12-09 14:22 ` S, Deepak
2013-12-08 8:46 ` [PATCH 2/4] drm/i915: set min delay to rpe delay (Efficient frequency) for better performace deepak.s
2013-12-08 16:07 ` Chris Wilson
2013-12-09 13:58 ` S, Deepak
2013-12-08 8:46 ` [PATCH 3/4] drm/i915: Disable/Enable PM Intrrupts based on the current freq deepak.s
2013-12-09 8:11 ` Daniel Vetter
2013-12-09 10:11 ` Ville Syrjälä
2013-12-10 9:44 ` S, Deepak
2013-12-08 8:46 ` [PATCH 4/4] drm/i915: WA to fix Voltage is not getting dropped to Vmin when Gfx is power gated deepak.s
2013-12-09 8:35 ` 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=1386492406-24716-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