dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Karthik B S <karthik.b.s@intel.com>
To: "Michel Dänzer" <michel@daenzer.net>,
	"Paulo Zanoni" <paulo.r.zanoni@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: vandita.kulkarni@intel.com, uma.shankar@intel.com,
	nicholas.kazlauskas@amd.com, dri-devel@lists.freedesktop.org,
	daniel.vetter@intel.com
Subject: Re: [PATCH v5 1/5] drm/i915: Add enable/disable flip done and flip done handler
Date: Wed, 5 Aug 2020 19:16:30 +0530	[thread overview]
Message-ID: <377c8569-cc3b-e1a8-3d1c-5a6cc9bfd99b@intel.com> (raw)
In-Reply-To: <f00f637e-639e-5d12-83bd-274ad0a23abe@daenzer.net>



On 7/27/2020 5:57 PM, Michel Dänzer wrote:
> On 2020-07-25 1:26 a.m., Paulo Zanoni wrote:
>> Em seg, 2020-07-20 às 17:01 +0530, Karthik B S escreveu:
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
>>> index 1fa67700d8f4..95953b393941 100644
>>> --- a/drivers/gpu/drm/i915/i915_irq.c
>>> +++ b/drivers/gpu/drm/i915/i915_irq.c
>>> @@ -697,14 +697,24 @@ u32 i915_get_vblank_counter(struct drm_crtc *crtc)
>>>   	return (((high1 << 8) | low) + (pixel >= vbl_start)) & 0xffffff;
>>>   }
>>>   
>>> +static u32 g4x_get_flip_counter(struct drm_crtc *crtc)
>>> +{
>>> +	struct drm_i915_private *dev_priv = to_i915(crtc->dev);
>>> +	enum pipe pipe = to_intel_crtc(crtc)->pipe;
>>> +
>>> +	return I915_READ(PIPE_FLIPCOUNT_G4X(pipe));
>>> +}
>>> +
>>>   u32 g4x_get_vblank_counter(struct drm_crtc *crtc)
>>>   {
>>>   	struct drm_i915_private *dev_priv = to_i915(crtc->dev);
>>>   	enum pipe pipe = to_intel_crtc(crtc)->pipe;
>>>   
>>> +	if (crtc->state->async_flip)
>>> +		return g4x_get_flip_counter(crtc);
>>> +
>>>   	return I915_READ(PIPE_FRMCOUNT_G4X(pipe));
>>
>> I don't understand the intention behind this, can you please clarify?
>> This goes back to my reply of the cover letter. It seems that here
>> we're going to alternate between two different counters in our vblank
>> count. So if user space alternates between sometimes using async flips
>> and sometimes using normal flip it's going to get some very weird
>> deltas, isn't it? At least this is what I remember from when I played
>> with these registers: FLIPCOUNT drifts away from FRMCOUNT when we start
>> using async flips.
> 
> This definitely looks wrong. The counter value returned by the
> get_vblank_counter hook is supposed to increment when a vertical blank
> period occurs; page flips are not supposed to affect this in any way.
> 

Thanks for the review.
As per the feedback received, I will be removing this and will revert 
back to the original implementation in the next revision.

Thanks,
Karthik.B.S
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-08-05 13:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 11:31 [PATCH v5 0/5] Asynchronous flip implementation for i915 Karthik B S
2020-07-20 11:31 ` [PATCH v5 1/5] drm/i915: Add enable/disable flip done and flip done handler Karthik B S
2020-07-24 23:26   ` Paulo Zanoni
2020-07-27 12:27     ` Michel Dänzer
2020-07-27 21:34       ` Daniel Vetter
2020-08-05 13:53         ` Karthik B S
2020-08-05 13:46       ` Karthik B S [this message]
2020-08-05 13:43     ` Karthik B S
2020-07-20 11:31 ` [PATCH v5 2/5] drm/i915: Add support for async flips in I915 Karthik B S
2020-07-24 23:26   ` Paulo Zanoni
2020-07-28  7:37     ` Karthik B S
2020-07-20 11:31 ` [PATCH v5 3/5] drm/i915: Add checks specific to async flips Karthik B S
2020-07-20 11:31 ` [PATCH v5 4/5] drm/i915: Do not call drm_crtc_arm_vblank_event in " Karthik B S
2020-07-20 11:31 ` [PATCH v5 5/5] drm/i915: Enable async flips in i915 Karthik B S
2020-07-24 23:26 ` [PATCH v5 0/5] Asynchronous flip implementation for i915 Paulo Zanoni
2020-07-29  7:23   ` Kulkarni, Vandita
2020-07-29  7:33     ` Michel Dänzer
2020-08-04  5:49       ` Kulkarni, Vandita
2020-08-04  6:06         ` Karthik B 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=377c8569-cc3b-e1a8-3d1c-5a6cc9bfd99b@intel.com \
    --to=karthik.b.s@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michel@daenzer.net \
    --cc=nicholas.kazlauskas@amd.com \
    --cc=paulo.r.zanoni@intel.com \
    --cc=uma.shankar@intel.com \
    --cc=vandita.kulkarni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).