Re: RFC for a render API to support adaptive sync and VRR

It would be really nice to have support for the automatic extension-less fullscreen game scenario. Maybe you don't have to solve everything in the first implementation... So a friendly ping here! Regards //Ernst Den tis 24 apr. 2018 kl 23:58 skrev Daniel Vetter : > > On Tue, Apr 24, 2018 at 4:28

Re: RFC for a render API to support adaptive sync and VRR

On Tue, Apr 24, 2018 at 4:28 PM, Harry Wentland wrote: > > > On 2018-04-24 08:09 AM, Daniel Vetter wrote: >> On Mon, Apr 23, 2018 at 02:19:44PM -0700, Manasi Navare wrote: >>> On Mon, Apr 23, 2018 at 10:40:06AM -0400, Harry Wentland wrote: On 2018-04-20 04:32 PM,

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-24 08:09 AM, Daniel Vetter wrote: > On Mon, Apr 23, 2018 at 02:19:44PM -0700, Manasi Navare wrote: >> On Mon, Apr 23, 2018 at 10:40:06AM -0400, Harry Wentland wrote: >>> On 2018-04-20 04:32 PM, Manasi Navare wrote: On Wed, Apr 18, 2018 at 09:39:02AM +0200, Daniel Vetter wrote:

RE: RFC for a render API to support adaptive sync and VRR

> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter > Sent: Tuesday, April 24, 2018 08:10 > On Mon, Apr 23, 2018 at 02:19:44PM -0700, Manasi Navare wrote: > > On Mon, Apr 23, 2018 at 10:40:06AM -0400, Harry Wentland wrote: > > > On 2018-04-20 04:32 PM, Manasi Navare

Re: RFC for a render API to support adaptive sync and VRR

On Mon, Apr 23, 2018 at 02:19:44PM -0700, Manasi Navare wrote: > On Mon, Apr 23, 2018 at 10:40:06AM -0400, Harry Wentland wrote: > > On 2018-04-20 04:32 PM, Manasi Navare wrote: > > > On Wed, Apr 18, 2018 at 09:39:02AM +0200, Daniel Vetter wrote: > > >> On Wed, Apr 18, 2018 at 5:58 AM, Keith

Re: RFC for a render API to support adaptive sync and VRR

On Mon, Apr 23, 2018 at 10:40:06AM -0400, Harry Wentland wrote: > On 2018-04-20 04:32 PM, Manasi Navare wrote: > > On Wed, Apr 18, 2018 at 09:39:02AM +0200, Daniel Vetter wrote: > >> On Wed, Apr 18, 2018 at 5:58 AM, Keith Packard wrote: > >>> Michel Dänzer

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-20 04:32 PM, Manasi Navare wrote: > On Wed, Apr 18, 2018 at 09:39:02AM +0200, Daniel Vetter wrote: >> On Wed, Apr 18, 2018 at 5:58 AM, Keith Packard wrote: >>> Michel Dänzer writes: Time-based presentation seems to be the right approach for

Re: RFC for a render API to support adaptive sync and VRR

Hi, On 20 April 2018 at 21:32, Manasi Navare wrote: > On Wed, Apr 18, 2018 at 09:39:02AM +0200, Daniel Vetter wrote: >> On Wed, Apr 18, 2018 at 5:58 AM, Keith Packard wrote: >> > I'd also encourage using a single unit for all of these values, >> >

Re: RFC for a render API to support adaptive sync and VRR

On Wed, Apr 18, 2018 at 5:58 AM, Keith Packard wrote: > Michel Dänzer writes: >> Time-based presentation seems to be the right approach for preventing >> micro-stutter in games as well, Croteam developers have been researching >> this. > > Both the Vulkan

Re: RFC for a render API to support adaptive sync and VRR

Michel Dänzer writes: > Time-based presentation seems to be the right approach for preventing > micro-stutter in games as well, Croteam developers have been researching > this. Both the Vulkan GOOGLE_display_timing extension and X11 Present extension offer the ability to

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-12 05:38 PM, Stéphane Marchesin wrote: > On Tue, Apr 10, 2018 at 12:37 AM, Michel Dänzer wrote: >> On 2018-04-10 08:45 AM, Christian König wrote: >>> Am 09.04.2018 um 23:45 schrieb Manasi Navare: Thanks for initiating the discussion. Find my comments below:

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-13 12:04 PM, Daniel Vetter wrote: > On Mon, Apr 09, 2018 at 04:00:21PM -0400, Harry Wentland wrote: >> Adding dri-devel, which I should've included from the start. > > Top posting, because I'm lazy and was out sick ... > > Few observations: > - Stéphane has a great point which seems

Re: RFC for a render API to support adaptive sync and VRR

On Mon, Apr 09, 2018 at 04:00:21PM -0400, Harry Wentland wrote: > Adding dri-devel, which I should've included from the start. Top posting, because I'm lazy and was out sick ... Few observations: - Stéphane has a great point which seems to have been ignored thus far. - Where's the VK extension

Re: RFC for a render API to support adaptive sync and VRR

On Tue, Apr 10, 2018 at 12:37 AM, Michel Dänzer wrote: > On 2018-04-10 08:45 AM, Christian König wrote: >> Am 09.04.2018 um 23:45 schrieb Manasi Navare: >>> Thanks for initiating the discussion. Find my comments below: >>> On Mon, Apr 09, 2018 at 04:00:21PM -0400, Harry

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-12 07:39 AM, Nicolai Hähnle wrote: > On 12.04.2018 01:30, Cyr, Aric wrote: >>> At least with VDPAU, video players are already explicitly specifying the >>> target presentation time, so no changes should be required at that >>> level. Don't know about other video APIs. >>> >>> The X11

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-12 01:39 PM, Nicolai Hähnle wrote: > On 12.04.2018 01:30, Cyr, Aric wrote: >>> At least with VDPAU, video players are already explicitly specifying the >>> target presentation time, so no changes should be required at that >>> level. Don't know about other video APIs. >>> >>> The X11

Re: RFC for a render API to support adaptive sync and VRR

On 12.04.2018 01:30, Cyr, Aric wrote: At least with VDPAU, video players are already explicitly specifying the target presentation time, so no changes should be required at that level. Don't know about other video APIs. The X11 Present extension protocol is also prepared for specifying the

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-12 01:30 AM, Cyr, Aric wrote: >> From: Michel Dänzer [mailto:mic...@daenzer.net] >> Sent: Wednesday, April 11, 2018 05:50 >> On 2018-04-11 08:57 AM, Nicolai Hähnle wrote: >>> On 10.04.2018 23:45, Cyr, Aric wrote: How does it work fine today given that all kernel seems to know is

RE: RFC for a render API to support adaptive sync and VRR

> From: Michel Dänzer [mailto:mic...@daenzer.net] > Sent: Wednesday, April 11, 2018 05:50 > On 2018-04-11 08:57 AM, Nicolai Hähnle wrote: > > On 10.04.2018 23:45, Cyr, Aric wrote: > >> How does it work fine today given that all kernel seems to know is > >> 'current' or 'current+1' vsyncs. > >>

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 06:26 PM, Cyr, Aric wrote:> > My guess is they prefer to “do nothing” and let driver/HW manage it, > otherwise you exempt all existing games from supporting adaptive sync > without a rewrite or update. Nobody is saying adaptive sync should only work with explicit target presentation

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 07:25 PM, Cyr, Aric wrote: >> From: Michel Dänzer [mailto:mic...@daenzer.net] >> On 2018-04-10 07:13 PM, Cyr, Aric wrote: From: Michel Dänzer [mailto:mic...@daenzer.net] On 2018-04-10 06:26 PM, Cyr, Aric wrote: > From: Koenig, Christian Sent: Tuesday, April 10, 2018

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-11 08:57 AM, Nicolai Hähnle wrote: > On 10.04.2018 23:45, Cyr, Aric wrote: > For video games we have a similar situation where a frame is > rendered > for a certain world time and in the ideal case we would actually > display the frame at this world time.

Re: RFC for a render API to support adaptive sync and VRR

On 10.04.2018 23:45, Cyr, Aric wrote: For video games we have a similar situation where a frame is rendered for a certain world time and in the ideal case we would actually display the frame at this world time. That seems like it would be a poorly written game that flips like that, unless they

RE: RFC for a render API to support adaptive sync and VRR

> From: Manasi Navare [mailto:manasi.d.nav...@intel.com] > Sent: Tuesday, April 10, 2018 17:37 > To: Wentland, Harry > Cc: amd-gfx mailing list ; Daniel Vetter > ; Haehnle, Nicolai > ;

RE: RFC for a render API to support adaptive sync and VRR

> From: Haehnle, Nicolai > Sent: Tuesday, April 10, 2018 13:48 > On 10.04.2018 19:25, Cyr, Aric wrote: > >> -Original Message- > >> From: Michel Dänzer [mailto:mic...@daenzer.net] > >> Sent: Tuesday, April 10, 2018 13:16 > >> > >> On 2018-04-10 07:13 PM, Cyr, Aric wrote: >

Re: RFC for a render API to support adaptive sync and VRR

On Tue, Apr 10, 2018 at 11:03:02AM -0400, Harry Wentland wrote: > Adding Anthony and Aric who've been working on Freesync with DC on other OSes > for a while. > > On 2018-04-09 05:45 PM, Manasi Navare wrote: > > Thanks for initiating the discussion. Find my comments below: > > > > On Mon, Apr

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 07:44 AM, Chris Wilson wrote: > Quoting Christian König (2018-04-10 07:45:04) >> Am 09.04.2018 um 23:45 schrieb Manasi Navare: >>> Properties that you mentioned above that the UMD can set before kernel can >>> enable VRR functionality >>> *bool vrr_enable or vrr_compatible >>>

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 01:52 PM, Harry Wentland wrote: > On 2018-04-10 12:37 PM, Nicolai Hähnle wrote: >> On 10.04.2018 18:26, Cyr, Aric wrote: >>> That presentation time doesn’t need to come to kernel as such and actually >>> is fine as-is completely decoupled from adaptive sync.  As long as the >>>

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 12:37 PM, Nicolai Hähnle wrote: > On 10.04.2018 18:26, Cyr, Aric wrote: >> That presentation time doesn’t need to come to kernel as such and actually >> is fine as-is completely decoupled from adaptive sync.  As long as the video >> player provides the new target_frame_duration_ns

Re: RFC for a render API to support adaptive sync and VRR

On 10.04.2018 19:25, Cyr, Aric wrote: -Original Message- From: Michel Dänzer [mailto:mic...@daenzer.net] Sent: Tuesday, April 10, 2018 13:16 On 2018-04-10 07:13 PM, Cyr, Aric wrote: -Original Message- From: Michel Dänzer [mailto:mic...@daenzer.net] Sent: Tuesday, April 10, 2018

RE: RFC for a render API to support adaptive sync and VRR

> -Original Message- > From: Michel Dänzer [mailto:mic...@daenzer.net] > Sent: Tuesday, April 10, 2018 13:16 > > On 2018-04-10 07:13 PM, Cyr, Aric wrote: > >> -Original Message- > >> From: Michel Dänzer [mailto:mic...@daenzer.net] > >> Sent: Tuesday, April 10, 2018 13:06 > >> On

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 07:13 PM, Cyr, Aric wrote: >> -Original Message- >> From: Michel Dänzer [mailto:mic...@daenzer.net] >> Sent: Tuesday, April 10, 2018 13:06 >> On 2018-04-10 06:26 PM, Cyr, Aric wrote: >>> From: Koenig, Christian Sent: Tuesday, April 10, 2018 11:43 >>> For video games we

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 05:35 PM, Cyr, Aric wrote: >> On 2018-04-10 03:37 AM, Michel Dänzer wrote: >>> On 2018-04-10 08:45 AM, Christian König wrote: Am 09.04.2018 um 23:45 schrieb Manasi Navare: > Thanks for initiating the discussion. Find my comments > below: On Mon, Apr 09, 2018 at

RE: RFC for a render API to support adaptive sync and VRR

> -Original Message- > From: Michel Dänzer [mailto:mic...@daenzer.net] > Sent: Tuesday, April 10, 2018 13:06 > On 2018-04-10 06:26 PM, Cyr, Aric wrote: > > From: Koenig, Christian Sent: Tuesday, April 10, 2018 11:43 > > > >> For video games we have a similar situation where a frame is

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 06:26 PM, Cyr, Aric wrote: > From: Koenig, Christian Sent: Tuesday, April 10, 2018 11:43 > >> For video games we have a similar situation where a frame is rendered >> for a certain world time and in the ideal case we would actually >> display the frame at this world time. > > That

Re: RFC for a render API to support adaptive sync and VRR

On 10.04.2018 18:26, Cyr, Aric wrote: That presentation time doesn’t need to come to kernel as such and actually is fine as-is completely decoupled from adaptive sync.  As long as the video player provides the new target_frame_duration_ns on the flip, then the driver/HW will target the correct

Re: RFC for a render API to support adaptive sync and VRR

Am 10.04.2018 um 17:35 schrieb Cyr, Aric: -Original Message- From: Wentland, Harry Sent: Tuesday, April 10, 2018 11:08 To: Michel Dänzer ; Koenig, Christian ; Manasi Navare Cc: Haehnle, Nicolai

RE: RFC for a render API to support adaptive sync and VRR

> -Original Message- > From: Wentland, Harry > Sent: Tuesday, April 10, 2018 11:08 > To: Michel Dänzer ; Koenig, Christian > ; Manasi Navare > > Cc: Haehnle, Nicolai ; Daniel Vetter >

Re: RFC for a render API to support adaptive sync and VRR

Am 10.04.2018 um 17:08 schrieb Harry Wentland: On 2018-04-10 03:37 AM, Michel Dänzer wrote: On 2018-04-10 08:45 AM, Christian König wrote: Am 09.04.2018 um 23:45 schrieb Manasi Navare: Thanks for initiating the discussion. Find my comments below: On Mon, Apr 09, 2018 at 04:00:21PM -0400,

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 03:37 AM, Michel Dänzer wrote: > On 2018-04-10 08:45 AM, Christian König wrote: >> Am 09.04.2018 um 23:45 schrieb Manasi Navare: >>> Thanks for initiating the discussion. Find my comments below: >>> On Mon, Apr 09, 2018 at 04:00:21PM -0400, Harry Wentland wrote: On 2018-04-09

Re: RFC for a render API to support adaptive sync and VRR

Adding Anthony and Aric who've been working on Freesync with DC on other OSes for a while. On 2018-04-09 05:45 PM, Manasi Navare wrote: > Thanks for initiating the discussion. Find my comments below: > > On Mon, Apr 09, 2018 at 04:00:21PM -0400, Harry Wentland wrote: >> Adding dri-devel, which

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-10 08:45 AM, Christian König wrote: > Am 09.04.2018 um 23:45 schrieb Manasi Navare: >> Thanks for initiating the discussion. Find my comments below: >> On Mon, Apr 09, 2018 at 04:00:21PM -0400, Harry Wentland wrote: >>> On 2018-04-09 03:56 PM, Harry Wentland wrote: === A DRM

Re: RFC for a render API to support adaptive sync and VRR

Am 09.04.2018 um 23:45 schrieb Manasi Navare: Thanks for initiating the discussion. Find my comments below: On Mon, Apr 09, 2018 at 04:00:21PM -0400, Harry Wentland wrote: Adding dri-devel, which I should've included from the start. On 2018-04-09 03:56 PM, Harry Wentland wrote: === What is

Re: RFC for a render API to support adaptive sync and VRR

Thanks for initiating the discussion. Find my comments below: On Mon, Apr 09, 2018 at 04:00:21PM -0400, Harry Wentland wrote: > Adding dri-devel, which I should've included from the start. > > On 2018-04-09 03:56 PM, Harry Wentland wrote: > > === What is adaptive sync and VRR? === > > > >

Re: RFC for a render API to support adaptive sync and VRR

Adding dri-devel, which I should've included from the start. On 2018-04-09 03:56 PM, Harry Wentland wrote: > === What is adaptive sync and VRR? === > > Adaptive sync has been part of the DisplayPort spec for a while now and > allows graphics adapters to drive displays with varying frame