From: Ramalingam C <ramalingam.c@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org, daniel.vetter@ffwll.ch,
rodrigo.vivi@intel.com, paulo.r.zanoni@intel.com
Subject: Re: [PATCH] drm/i915: drrs_invalidate at flip schedule
Date: Fri, 15 May 2015 18:54:54 +0530 [thread overview]
Message-ID: <5555F3A6.7060903@intel.com> (raw)
In-Reply-To: <20150515115841.GE17226@nuc-i3427.alporthouse.com>
On Friday 15 May 2015 05:28 PM, Chris Wilson 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>
> Just Cc: Chris Wilson <chris@chris-wilson.co.uk>
> References: https://bugs.freedesktop.org/show_bug.cgi?id=90418
>
> Ok, looks correct. This invalidate will be paired with a flush after the
> flip completes to reschedule the downclock of the refresh rates.
>
> I think a comment would be useful to explain the relationship here, or
> better would be a new intel_edp_drrs_flip_prepare() stub so that the
> internal details of drrs are kept out of intel_frontbuffer.c and the
> comment can refer to the adjacent functions for reference.
But in flip preparation we would want to invalidate the PSR (software
implementation) also.
In that case we could create a function called
intel_frontbuffer_flip_invalidate() instead of edp_drrs_flip_prepare.
This will be invoking the invalidation for the PSR and DRRS. And this
function could be called from
intel_frontbuffer_flip_prepare().
Incase If FBC invalidate also needed at flip preparation, then we could
create a common function called
intel_frontbuffer_invalidate parallel to intel_frontbuffer_flush which
will be used by
intel_fb_obj_invalidate and intel_frontbuffer_flip_prepare.
Please share your view. whether FBC invalidate is required on flip
preparation?
> -Chris
>
--
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-05-15 13:31 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 [this message]
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
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=5555F3A6.7060903@intel.com \
--to=ramalingam.c@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@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.