public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "S, Deepak" <deepak.s@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4 2/2] drm/i915/vlv: WA to fix Voltage not getting dropped to Vmin when Gfx is power gated.
Date: Wed, 29 Jan 2014 10:09:21 +0530	[thread overview]
Message-ID: <52E885F9.703@intel.com> (raw)
In-Reply-To: <20140128193345.GE7444@phenom.ffwll.local>



On 1/29/2014 1:03 AM, Daniel Vetter wrote:
> On Tue, Jan 28, 2014 at 08:02:56PM +0530, S, Deepak wrote:
>>
>>
>> On 1/27/2014 10:22 PM, Daniel Vetter wrote:
>>> On Mon, Jan 27, 2014 at 09:35:06PM +0530, deepak.s@intel.com wrote:
>>>> From: Deepak S <deepak.s@intel.com>
>>>>
>>>> When we enter RC6 and GFX Clocks are off, the voltage remains higher
>>>> than Vmin. When we try to set the freq to RPn, it might fail since the
>>>> Gfx clocks are down. So to fix this in Gfx idle, Bring the GFX clock up
>>>> and set the freq to RPn then move GFx down.
>>>>
>>>> v2: remove vlv_update_rps_cur_delay function. Update commit message (Daniel)
>>>>
>>>> v3: Fix the timeout during wait for gfx clock (Jesse)
>>>>
>>>> v4: addressed comments on set freq and punit wait (Ville)
>>>>
>>>> Signed-off-by: Deepak S <deepak.s@intel.com>
>>>> ---
>>>>   drivers/gpu/drm/i915/i915_reg.h |  4 ++++
>>>>   drivers/gpu/drm/i915/intel_pm.c | 53 ++++++++++++++++++++++++++++++++++++++++-
>>>>   2 files changed, 56 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
>>>> index 242f540..feaa83b 100644
>>>> --- a/drivers/gpu/drm/i915/i915_reg.h
>>>> +++ b/drivers/gpu/drm/i915/i915_reg.h
>>>> @@ -4944,6 +4944,10 @@
>>>>   						 GEN6_PM_RP_DOWN_THRESHOLD | \
>>>>   						 GEN6_PM_RP_DOWN_TIMEOUT)
>>>>
>>>> +#define VLV_GTLC_SURVIVABILITY_REG              0x130098
>>>> +#define VLV_GFX_CLK_STATUS_BIT			(1<<3)
>>>> +#define VLV_GFX_CLK_FORCE_ON_BIT		(1<<2)
>>>> +
>>>>   #define GEN6_GT_GFX_RC6_LOCKED			0x138104
>>>>   #define VLV_COUNTER_CONTROL			0x138104
>>>>   #define   VLV_COUNT_RANGE_HIGH			(1<<15)
>>>> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
>>>> index c6a07c9..84e20d0 100644
>>>> --- a/drivers/gpu/drm/i915/intel_pm.c
>>>> +++ b/drivers/gpu/drm/i915/intel_pm.c
>>>> @@ -3035,6 +3035,56 @@ void gen6_set_rps(struct drm_device *dev, u8 val)
>>>>   	trace_intel_gpu_freq_change(val * 50);
>>>>   }
>>>>
>>>> +/* vlv_set_rps_idle: Set the frequency to Rpn if Gfx clocks are down
>>>> + *
>>>> + * * If Gfx is Idle, then
>>>> + * 1. Mask Turbo interrupts
>>>> + * 2. Bring up Gfx clock
>>>> + * 3. Change the freq to Rpn and wait till P-Unit updates freq
>>>> + * 4. Clear the Force GFX CLK ON bit so that Gfx can down
>>>> + * 5. Unmask Turbo interrupts
>>>> +*/
>>>> +static void vlv_set_rps_idle(struct drm_i915_private *dev_priv)
>>>> +{
>>>> +	/*
>>>> +	 * When we are idle.  Drop to min voltage state.
>>>> +	 */
>>>> +
>>>> +	if (dev_priv->rps.cur_delay <= dev_priv->rps.min_delay)
>>>> +		return;
>>>> +
>>>> +	/* Mask turbo interrupt so that they will not come in between */
>>>> +	I915_WRITE(GEN6_PMINTRMSK, 0xffffffff);
>>>> +
>>>> +	/* Bring up the Gfx clock */
>>>> +	I915_WRITE(VLV_GTLC_SURVIVABILITY_REG,
>>>> +		I915_READ(VLV_GTLC_SURVIVABILITY_REG) |
>>>> +				VLV_GFX_CLK_FORCE_ON_BIT);
>>>> +
>>>> +	if (wait_for_atomic(((VLV_GFX_CLK_STATUS_BIT &
>>>
>>> Do we really need an atomic register busy loop here? Afaics this is only
>>> called from process context, so the normal wait_for macro should be good
>>> enough ...
>>> -Daniel
>> I agree, the reason why i did the _atomic as we observed delay in
>> scheduling the wait_for and we ended up spending lot of time here.
>> I will wait for other comments, If i dont get any, I will address
>> this comment and submit the patch.
>
> Now that we're using Chris' idle-clamping rps logic this would be run from
> a work queue. So I hope that the potential scheduling delays here won't
> affect things badly. If it does you can stick with the _atomic, but then
> it needs a comment.
>
> But I really hope that we only call this from worker threads, so shouldn't
> matter too badly if there's a bit a scheduler delay.
> -Daniel

I verified and we don't have a scheduling delays, I will change this to 
_atomic to wait_for

-Deepak
>>
>>>> +		I915_READ(VLV_GTLC_SURVIVABILITY_REG)) != 0), 5)) {
>>>> +			DRM_ERROR("GFX_CLK_ON request timed out\n");
>>>> +		return;
>>>> +	}
>>>> +
>>>> +	vlv_punit_write(dev_priv, PUNIT_REG_GPU_FREQ_REQ, dev_priv->rps.min_delay);
>>>> +
>>>> +	if (wait_for_atomic(((vlv_punit_read(dev_priv, PUNIT_REG_GPU_FREQ_STS))
>>>> +				& GENFREQSTATUS) == 0, 5))
>>>> +		DRM_DEBUG_DRIVER("timed out waiting for Punit\n");
>>>> +
>>>> +	/* Release the Gfx clock */
>>>> +	I915_WRITE(VLV_GTLC_SURVIVABILITY_REG,
>>>> +		I915_READ(VLV_GTLC_SURVIVABILITY_REG) &
>>>> +				~VLV_GFX_CLK_FORCE_ON_BIT);
>>>> +
>>>> +	/* Unmask Turbo interrupts */
>>>> +	I915_WRITE(GEN6_PMINTRMSK, ~(GEN6_PM_RPS_EVENTS |
>>>> +					GEN6_PM_RP_UP_EI_EXPIRED));
>>>> +}
>>>> +
>>>> +
>>>> +
>>>>   void gen6_rps_idle(struct drm_i915_private *dev_priv)
>>>>   {
>>>>   	struct drm_device *dev = dev_priv->dev;
>>>> @@ -3042,7 +3092,7 @@ 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))
>>>> -			valleyview_set_rps(dev_priv->dev, dev_priv->rps.min_delay);
>>>> +			vlv_set_rps_idle(dev_priv);
>>>>   		else
>>>>   			gen6_set_rps(dev_priv->dev, dev_priv->rps.min_delay);
>>>>   		dev_priv->rps.last_adj = 0;
>>>> @@ -4273,6 +4323,7 @@ void intel_gpu_ips_teardown(void)
>>>>   	i915_mch_dev = NULL;
>>>>   	spin_unlock_irq(&mchdev_lock);
>>>>   }
>>>> +
>>>>   static void intel_init_emon(struct drm_device *dev)
>>>>   {
>>>>   	struct drm_i915_private *dev_priv = dev->dev_private;
>>>> --
>>>> 1.8.5.2
>>>>
>>>> _______________________________________________
>>>> Intel-gfx mailing list
>>>> Intel-gfx@lists.freedesktop.org
>>>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>>>
>

  reply	other threads:[~2014-01-29  4:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 16:05 [PATCH v5 0/2] VLV Turbo/rps + RC6 workaround deepak.s
2014-01-27 16:05 ` [PATCH v5 1/2] drm/i915: Disable/Enable PM Intrrupts based on the current freq deepak.s
     [not found]   ` <F359EE24E0B97E4A9739736D2C188EF3010089D9@BGSMSX104.gar.corp.intel.com>
2014-01-29 15:45     ` S, Deepak
2014-01-29 15:59   ` Ville Syrjälä
2014-01-29 19:30     ` Daniel Vetter
2014-01-30  7:03       ` S, Deepak
2014-01-27 16:05 ` [PATCH v4 2/2] drm/i915/vlv: WA to fix Voltage not getting dropped to Vmin when Gfx is power gated deepak.s
2014-01-27 16:52   ` Daniel Vetter
2014-01-28 14:32     ` S, Deepak
2014-01-28 19:33       ` Daniel Vetter
2014-01-29  4:39         ` S, Deepak [this message]
2014-01-27 17:07   ` Ville Syrjälä
2014-01-28 14:17     ` 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=52E885F9.703@intel.com \
    --to=deepak.s@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