From: Ramalingam C <ramalingam.c@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
rodrigo.vivi@intel.com, paulo.r.zanoni@intel.com
Subject: Re: [PATCH] drm/i915: drrs_invalidate at flip schedule
Date: Thu, 11 Jun 2015 14:57:52 +0530 [thread overview]
Message-ID: <55795498.60007@intel.com> (raw)
In-Reply-To: <20150518082022.GL15256@phenom.ffwll.local>
Sorry for late response. I was away for longer.
Daniel,
As we have the intel_frontbuffer_flush, I have created the
intel_frontbuffer_invalidate.
This can be called from flip preparation notification to handle the
frontbuffer invalidation.
I will share the patches now.
On Monday 18 May 2015 01:50 PM, Daniel Vetter wrote:
> On Fri, May 15, 2015 at 02:08:22AM +0530, Ramalingam C wrote:
>> After scheduling a flip for obj, we are supposed to invalidate the
>> drrs.
>>
>> Action:
>> Adding a call to intel_edp_drrs_invalidate at
>> intel_frontbuffer_flip_prepare.
>>
>> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> ---
>> drivers/gpu/drm/i915/intel_frontbuffer.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_frontbuffer.c b/drivers/gpu/drm/i915/intel_frontbuffer.c
>> index 57095f5..44387ed 100644
>> --- a/drivers/gpu/drm/i915/intel_frontbuffer.c
>> +++ b/drivers/gpu/drm/i915/intel_frontbuffer.c
>> @@ -244,6 +244,7 @@ void intel_frontbuffer_flip_prepare(struct drm_device *dev,
>> dev_priv->fb_tracking.busy_bits &= ~frontbuffer_bits;
>> mutex_unlock(&dev_priv->fb_tracking.lock);
>>
>> + intel_edp_drrs_invalidate(dev, frontbuffer_bits);
> Nope. The problem here is that drrs wants business, but the frontbuffer
> tracking only gives you coherency signals (flush/invalidate). But for
> business both flush and invalidate indicate that there's something going
> on on the screen. Which means you _must_ uplock the display in both
> drrs_flush and drrs_invalidate.
>
> By applaying the upclocking only to the flip codepath you're only papering
> over this bug in one specific case, but not for all the other paths where
> frontbuffer rendering is possible.
> -Daniel
>
>> intel_psr_single_frame_update(dev);
>> }
>>
>> --
>> 1.7.9.5
>>
--
Thanks,
--Ram
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-11 9:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 20:38 [PATCH] drm/i915: drrs_invalidate at flip schedule Ramalingam C
2015-05-15 11:58 ` Chris Wilson
2015-05-15 13:24 ` Ramalingam C
2015-05-15 13:56 ` Chris Wilson
2015-05-18 2:49 ` shuang.he
2015-05-18 8:20 ` Daniel Vetter
2015-06-11 9:27 ` Ramalingam C [this message]
2015-06-15 9:52 ` Daniel Vetter
2015-06-15 15:15 ` Ramalingam C
2015-06-15 15:20 ` [PATCH] drm/i915: Restarting the Idleness DRRS in drrs_flush Ramalingam C
2015-06-15 15:46 ` Daniel Vetter
2015-06-11 9:38 ` [PATCH 1/2] drm/i915: fb_obj invalidate is divided into two functions Ramalingam C
2015-06-11 9:38 ` [PATCH 2/2] drm/i915: frontbuffer invalidate at flip schedule Ramalingam C
2015-06-11 9:56 ` Chris Wilson
2015-06-11 10:57 ` Ramalingam C
2015-06-14 20:59 ` 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=55795498.60007@intel.com \
--to=ramalingam.c@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.