Re: [PATCH V9 00/43] Color Pipeline API w/ VKMS

[Harry Wentland <harry.wentland@amd.com>]

On 2025-05-22 11:27, Pekka Paalanen wrote:
> On Thu, 22 May 2025 09:54:50 -0400
> Harry Wentland <harry.wentland@amd.com> wrote:
> 
>> On 2025-05-22 09:49, Simon Ser wrote:
>>> On Thursday, May 22nd, 2025 at 15:28, Harry Wentland <harry.wentland@amd.com> wrote:
>>>   
>>>>>> What we should
>>>>>> do is reject YCbCr-type buffers with the color pipeline until we
>>>>>> implement support for COLOR_ENCODING and COLOR_RANGE as a new
>>>>>> CSC colorop.  
>>>>>
>>>>> Rejecting is fine, but is implementing COLOR_ENCODING and COLOR_RANGE
>>>>> really a good idea instead of making the color pipelines handle them?
>>>>>
>>>>> Wasn't the original plan to hide all such legacy plane properties when
>>>>> userspace signals color pipeline support?  
>>>>
>>>> It still is. But handling the color-space conversion via a new
>>>> colorop with two properties: COLOR_ENCODING and COLOR_RANGE
>>>> seemed to be the most straight-forward way of dealing with this.  
>>>
>>> I think everybody in this thread is suggesting that the old plane
>>> COLOR_ENCODING and COLOR_RANGE properties are rejected and will never
>>> be accepted again with the color pipeline. I think Harry is just saying
>>> that a new colorop can be introduced with encoding/range properties, but
>>> this is completely separate from the old props?
>>>   
>>
>> Correct. Thanks for clarifying.
> 
> Oh! Ok, that's cool. I thought we were talking about KMS plane
> properties and not a new colorop.
> 

My conciseness/verbosity filter just needed some tuning. :)

Harry

> 
> Thanks,
> pq