From: Deepak S <deepak.s@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Paulo Zanoni <przanoni@gmail.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2 3/4] drm/i915/chv: Set min freq to efficient frequency on chv
Date: Fri, 27 Mar 2015 10:24:16 +0530 [thread overview]
Message-ID: <5514E278.7010000@linux.intel.com> (raw)
In-Reply-To: <20150326214349.GH18055@nuc-i3427.alporthouse.com>
On Friday 27 March 2015 03:13 AM, Chris Wilson wrote:
> On Thu, Mar 26, 2015 at 06:32:15PM -0300, Paulo Zanoni wrote:
>> 2015-03-19 11:14 GMT-03:00 <deepak.s@linux.intel.com>:
>>> From: Deepak S <deepak.s@linux.intel.com>
>>>
>>> After feedback from the hardware team, now we set the GPU min/idel freq to RPe.
>>> Punit is expecting us to operate GPU between Rpe & Rp0. If we drop the
>>> frequency to RPn, punit is failing to change the input voltage to
>>> minimum :(
>> Since this is far away from the obvious, I am imagining some
>> programmer from the future looking at this code and imagining
>> min_freq_softlimit was "accidentally" set to RPe instead of RPn. Can't
>> we add a comment in the code - not just the commit message -, to make
>> it clear that we're doing this since the punit is weird?
>>
>> Another thing which I noticed is that your patch title mentions CHV,
>> but your patch touches the VLV function instead of the CHV one. This
>> also leads me to think that maybe the power measurement experiments
>> you did were done using the non-patched CHV code... Can you please
>> clarify your intentions here? And also maybe redo the power
>> measurements if needed.
>>
>> Also, I think we need at least an ACK from Chris here, especially
>> since he was already discussing the previous version of this patch.
> If you include a comment like (and note we want to set
> dev_priv->rps.min_freq not dev_priv->rps.min_freq_softlimit):
>
> /* PUnit validated range is only [RPe, RP0] */
> dev_priv->rps.min_freq = dev_priv->rps.efficient_freq;
>
> and make sure that is set before we derive dev_priv->rps.idle_freq.
>
> You can have my
> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
Thanks Chris. I will address comments & rebase the patch.
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-27 4:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 14:14 [PATCH v2 0/4] CHV PM fix & Improvements deepak.s
2015-03-19 14:14 ` [PATCH v2 1/4] drm/i915/chv: Remove Wait for a previous gfx force-off deepak.s
2015-03-19 14:14 ` [PATCH v2 2/4] drm/i915: Re-adjusting rc6 promotional timer for chv deepak.s
2015-03-26 21:02 ` Paulo Zanoni
2015-03-27 4:56 ` Deepak S
2015-03-19 14:14 ` [PATCH v2 3/4] drm/i915/chv: Set min freq to efficient frequency on chv deepak.s
2015-03-26 21:32 ` Paulo Zanoni
2015-03-26 21:43 ` Chris Wilson
2015-03-27 4:54 ` Deepak S [this message]
2015-03-19 14:14 ` [PATCH v2 4/4] drm/i915: Setup static bias for GPU deepak.s
2015-03-20 2:01 ` shuang.he
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=5514E278.7010000@linux.intel.com \
--to=deepak.s@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=przanoni@gmail.com \
/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