On 2021-01-15 14:29, John Stultz wrote:
On Thu, Jan 14, 2021 at 12:54 PM wrote:
On 2021-01-13 18:28, John Stultz wrote:
> On Wed, Jan 13, 2021 at 11:52 AM Veera Sundaram Sankaran
> wrote:
>>
>> The explicit out-fences in crtc are signaled as part of vblank event,
>> indicating all framebuffer
On 2021-01-13 18:28, John Stultz wrote:
On Wed, Jan 13, 2021 at 11:52 AM Veera Sundaram Sankaran
wrote:
The explicit out-fences in crtc are signaled as part of vblank event,
indicating all framebuffers present on the Atomic Commit request are
scanned out on the screen. Though the fence signal
On 2021-01-08 11:55, John Stultz wrote:
On Thu, Jan 7, 2021 at 12:53 AM Veera Sundaram Sankaran
wrote:
Some drivers have hardware capability to get the precise timestamp of
certain events based on which the fences are triggered. This allows it
to
set accurate timestamp factoring out any softw
On 2020-11-19 03:58, Daniel Vetter wrote:
On Thu, Nov 12, 2020 at 7:27 PM Veera Sundaram Sankaran
wrote:
Some drivers have hardware capability to get the precise timestamp of
certain events based on which the fences are triggered. This allows it
to set accurate timestamp factoring out any soft
On 2020-11-13 12:45, Daniel Vetter wrote:
On Thu, Nov 12, 2020 at 10:27:23AM -0800, Veera Sundaram Sankaran
wrote:
The explicit out-fences in crtc are signaled as part of vblank event,
indicating all framebuffers present on the Atomic Commit request are
scanned out on the screen. Though the fenc
On 2020-11-12 10:27, Veera Sundaram Sankaran wrote:
Some drivers have hardware capability to get the precise timestamp of
certain events based on which the fences are triggered. This allows it
to set accurate timestamp factoring out any software and IRQ latencies.
Move the timestamp parameter out
