public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Deepak S <deepak.s@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v3] drm/i915: Force GPU Freq to lowest while suspending.
Date: Fri, 20 Jun 2014 19:55:05 +0530	[thread overview]
Message-ID: <53A44441.3050403@linux.intel.com> (raw)
In-Reply-To: <CAKMK7uE0q+nDdqcU19i5nxwxBuiDHaK7x+ji70A2PoF4jV+SPg@mail.gmail.com>


On Thursday 19 June 2014 06:04 PM, Daniel Vetter wrote:
> On Fri, Jun 20, 2014 at 1:59 PM,  <deepak.s@linux.intel.com> wrote:
>> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
>> index 2043c4b..6bbb90b 100644
>> --- a/drivers/gpu/drm/i915/intel_pm.c
>> +++ b/drivers/gpu/drm/i915/intel_pm.c
>> @@ -4881,6 +4881,9 @@ void intel_suspend_gt_powersave(struct drm_device *dev)
>>          /* Interrupts should be disabled already to avoid re-arming. */
>>          WARN_ON(dev->irq_enabled);
>>
>> +       /* Force GPU to min freq during suspend */
>> +       gen6_rps_idle(dev_priv);
>> +
> Shouldn't this be _after_ we've cancelled the rps works? Otherwise the
> work item might sneak in and undo the idling between the idle and work
> cancelling.
> -Daniel

My mistake sending updated patch, -Deepak

  reply	other threads:[~2014-06-19 14:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18  0:00 [PATCH v2] drm/i915: Bring GPU Freq to min while suspending deepak.s
2014-06-17 22:17 ` Daniel Vetter
2014-06-19  3:23   ` Deepak S
2014-06-18 10:48     ` Daniel Vetter
2014-06-20 11:59   ` [PATCH v3] drm/i915: Force GPU Freq to lowest " deepak.s
2014-06-19 12:34     ` Daniel Vetter
2014-06-20 14:25       ` Deepak S [this message]
2014-06-20 14:33       ` [PATCH v4] " deepak.s
2014-07-15  7:35         ` Deepak S
2014-07-14 15:17           ` Jesse Barnes
2014-07-16  3:21             ` Deepak S

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=53A44441.3050403@linux.intel.com \
    --to=deepak.s@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