From: Deepak S <deepak.s@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/chv: Drop WaGsvBringDownFreqInRc6
Date: Wed, 16 Jul 2014 08:51:20 +0530 [thread overview]
Message-ID: <53C5EFB0.1070805@linux.intel.com> (raw)
In-Reply-To: <20140714081715.532fbe97@jbarnes-desktop>
On Monday 14 July 2014 08:47 PM, Jesse Barnes wrote:
> On Tue, 15 Jul 2014 13:03:55 +0530
> Deepak S <deepak.s@linux.intel.com> wrote:
>
>> On Saturday 28 June 2014 11:26 AM, deepak.s@linux.intel.com wrote:
>>> From: Deepak S <deepak.s@linux.intel.com>
>>>
>>> Drop WaGsvBringDownFreq on CHV.
>>> When in RC6 requesting the min freq should be fine to bring the
>>> voltage down.
>>>
>>> Signed-off-by: Deepak S <deepak.s@linux.intel.com>
>>> ---
>>> drivers/gpu/drm/i915/intel_pm.c | 4 +++-
>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
>>> index 6b6cfd4..4875f745 100644
>>> --- a/drivers/gpu/drm/i915/intel_pm.c
>>> +++ b/drivers/gpu/drm/i915/intel_pm.c
>>> @@ -3253,7 +3253,9 @@ void gen6_rps_idle(struct drm_i915_private *dev_priv)
>>>
>>> mutex_lock(&dev_priv->rps.hw_lock);
>>> if (dev_priv->rps.enabled) {
>>> - if (IS_VALLEYVIEW(dev))
>>> + if (IS_CHERRYVIEW(dev))
>>> + valleyview_set_rps(dev_priv->dev, dev_priv->rps.min_freq_softlimit);
>>> + else if (IS_VALLEYVIEW(dev))
>>> vlv_set_rps_idle(dev_priv);
>>> else
>>> gen6_set_rps(dev_priv->dev, dev_priv->rps.min_freq_softlimit);
>> Hi Jesse,
>>
>> can you please review this patch?
> Reviewed-by: Jesse Barnes <jbarnes@Virtuousgeek.org>
>
Thanks for reviewing
prev parent reply other threads:[~2014-07-15 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 5:56 [PATCH] drm/i915/chv: Drop WaGsvBringDownFreqInRc6 deepak.s
2014-07-15 7:33 ` Deepak S
2014-07-14 15:17 ` Jesse Barnes
2014-07-14 17:27 ` Daniel Vetter
2014-07-16 3:21 ` Deepak S [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=53C5EFB0.1070805@linux.intel.com \
--to=deepak.s@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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