On Mon, 15 Oct 2018 12:06:52 +0200
Michel Dänzer wrote:
> On 2018-10-15 11:47 a.m., Christian König wrote:
> > Am 15.10.2018 um 11:40 schrieb Michel Dänzer:
> >> On 2018-10-13 7:38 p.m., Christian König wrote:
> >>> Am 12.10.2018 um 18:44 schrieb Nicholas Kazlauskas:
> This patch intro
On 2018-10-12 12:44 p.m., Nicholas Kazlauskas wrote:
> This patch introduces the 'vrr_enabled' CRTC property to allow
> dynamic control over variable refresh rate support for a CRTC.
>
> This property should be treated like a content hint to the driver -
> if the hardware or driver is not capable
Am 15.10.2018 um 12:06 schrieb Michel Dänzer:
> [SNIP]
> Apart from the above, another issue is that this would give direct
> control to the client on whether or not VRR should be used. But we want
> to allow the user to disable VRR even if a client wants to use it, via
> an RandR output property.
On 2018-10-15 11:47 a.m., Christian König wrote:
> Am 15.10.2018 um 11:40 schrieb Michel Dänzer:
>> On 2018-10-13 7:38 p.m., Christian König wrote:
>>> Am 12.10.2018 um 18:44 schrieb Nicholas Kazlauskas:
This patch introduces the 'vrr_enabled' CRTC property to allow
dynamic control over v
Am 15.10.2018 um 11:40 schrieb Michel Dänzer:
On 2018-10-13 7:38 p.m., Christian König wrote:
Am 12.10.2018 um 18:44 schrieb Nicholas Kazlauskas:
This patch introduces the 'vrr_enabled' CRTC property to allow
dynamic control over variable refresh rate support for a CRTC.
This property should b
On 2018-10-13 7:38 p.m., Christian König wrote:
> Am 12.10.2018 um 18:44 schrieb Nicholas Kazlauskas:
>> This patch introduces the 'vrr_enabled' CRTC property to allow
>> dynamic control over variable refresh rate support for a CRTC.
>>
>> This property should be treated like a content hint to the
Am 12.10.2018 um 18:44 schrieb Nicholas Kazlauskas:
This patch introduces the 'vrr_enabled' CRTC property to allow
dynamic control over variable refresh rate support for a CRTC.
This property should be treated like a content hint to the driver -
if the hardware or driver is not capable of drivin
This patch introduces the 'vrr_enabled' CRTC property to allow
dynamic control over variable refresh rate support for a CRTC.
This property should be treated like a content hint to the driver -
if the hardware or driver is not capable of driving variable refresh
timings then this is not considered
