[PATCH] drm/amdgpu add "pixel_encoding"

[Xaver Hugl]

Am Di., 5. Nov. 2024 um 16:16 Uhr schrieb Matias N. Goldberg
<dark_sylinc at yahoo.com.ar>:
>
> > That's not a problem, incompatible options can just be rejected in atomic tests.
>
> I was thinking from a user perspective. It'd be easier for user-space config apps to present only the valid options, rather than offering all possible combinations only to reject them after the user selected an invalid config (or perform hundreds of atomic tests every time we need to show a config dialog).
No, it's way easier to deal with 3 separate properties and have the
very simple logic (for which no atomic tests have to be made) in the
UI to prevent the user from setting obviously invalid combinations.
Having to split up an enum with tens or hundreds of values into
options the user can understand and that we can properly use is a lot
more effort.

> > opRGB is not supported by any screen I've ever looked at, so it doesn't surprise me that you'd get glitches.
>
> I don't know if it was just a fallback, but my screen *does* work when using opRGB with rgb encoding (it glitches when using yuv encoding).
That's most likely not because of the value of "opRGB", but just what
it does with all unsupported colorspace values.