Re: [PATCH] drm/atomic: add quirks for blind save/restore

2022-11-17 Thread Pekka Paalanen
On Thu, 17 Nov 2022 07:54:40 + Simon Ser wrote: > Two quirks to make blind atomic save/restore [1] work correctly: > > - Mark the DPMS property as immutable for atomic clients, since > atomic clients cannot change it. > - Allow user-space to set content protection to "enabled", interpret >

Re: [PATCH v3 0/6] Add support for atomic async page-flips

2022-11-17 Thread Simon Ser
Ville, any news on this?

Re: [PATCH] drm/atomic: add quirks for blind save/restore

2022-11-17 Thread Daniel Vetter
On Thu, Nov 17, 2022 at 07:54:40AM +, Simon Ser wrote: > Two quirks to make blind atomic save/restore [1] work correctly: > > - Mark the DPMS property as immutable for atomic clients, since > atomic clients cannot change it. > - Allow user-space to set content protection to "enabled", interp

Re: The state of Quantization Range handling

2022-11-17 Thread Sebastian Wick
Hi Dave, I noticed that I didn't get the Broadcast RGB property thanks to you (more below) On Tue, Nov 15, 2022 at 2:16 PM Dave Stevenson wrote: > > Hi Sebastian > > Thanks for starting the conversation - it's stalled a number of times > previously. > > On Mon, 14 Nov 2022 at 23:12, Sebastian Wi

Re: The state of Quantization Range handling

2022-11-17 Thread Sebastian Wick
Hi Yussuf, On Tue, Nov 15, 2022 at 5:26 PM Yussuf Khalil wrote: > > Hello Sebastian, > > I've previously done some work on this topic [1]. My efforts were mostly about > fixing the situation regarding overrides and providing proper means for > userspace. I am affected by the issue myself as I own

Re: The state of Quantization Range handling

2022-11-17 Thread Sebastian Wick
On Wed, Nov 16, 2022 at 1:34 PM Pekka Paalanen wrote: > > On Tue, 15 Nov 2022 00:11:56 +0100 > Sebastian Wick wrote: > > > There are still regular bug reports about monitors (sinks) and sources > > disagreeing about the quantization range of the pixel data. In > > particular sources sending full