> -Original Message-
> From: Ville Syrjälä
> Sent: Wednesday, September 23, 2020 4:05 PM
> To: Kulkarni, Vandita
> Cc: intel-gfx@lists.freedesktop.org; Nikula, Jani
> Subject: Re: [V13 5/5] drm/i915/dsi: Enable software vblank counter
>
> On Wed, Sep 23, 2020 at 10:16:05AM +, Kulkar
On Wed, Sep 23, 2020 at 10:16:05AM +, Kulkarni, Vandita wrote:
> > -Original Message-
> > From: Ville Syrjälä
> > Sent: Wednesday, September 23, 2020 3:30 PM
> > To: Kulkarni, Vandita
> > Cc: intel-gfx@lists.freedesktop.org; Nikula, Jani
> > Subject: Re: [V13 5/5] drm/i915/dsi: Enabl
> -Original Message-
> From: Ville Syrjälä
> Sent: Wednesday, September 23, 2020 3:30 PM
> To: Kulkarni, Vandita
> Cc: intel-gfx@lists.freedesktop.org; Nikula, Jani
> Subject: Re: [V13 5/5] drm/i915/dsi: Enable software vblank counter
>
> On Tue, Sep 22, 2020 at 07:14:26PM +0530, Vandit
On Tue, Sep 22, 2020 at 07:14:26PM +0530, Vandita Kulkarni wrote:
> In case of DSI cmd mode, we get hw vblank counter
> updated after the TE comes in, if we try to read
> the hw vblank counter in te handler we wouldnt have
> the udpated vblank counter yet.
> This will lead to a state where we would
In case of DSI cmd mode, we get hw vblank counter
updated after the TE comes in, if we try to read
the hw vblank counter in te handler we wouldnt have
the udpated vblank counter yet.
This will lead to a state where we would send the
vblank event to the user space in the next te,
though the frame up