On Thu, Sep 11, 2025 at 04:07:34PM +0300, Marius Vlad wrote: > From: Andri Yngvason <an...@yngvason.is> > > Adds a new general DRM property named "color format" which can be used by > userspace to force the display driver output a particular color format. > > Possible options are: > - auto (setup by default, driver internally picks the color format) > - rgb > - ycbcr444 > - ycbcr422 > - ycbcr420 > > Drivers should advertise from this list the formats which they support. > Together with this list and EDID data from the sink we should be able > to relay a list of usable color formats to users to pick from.
It's unclear, who should be combining this data: should it be the kernel or the userspace. >From my POV deferring this to the userspace doesn't make sense: there will be different quirks for monitors / panels, e.g. the EDID wrongly advertising YUV or not advertising a knowlingly-working capability. I think that the property should reflect the kernel view on the possible formats, which should be updated during get_modes() (or every time EDID is being read). And that's not to mention that there are enough use-cases where the connector doesn't have EDID at all. > > Signed-off-by: Werner Sembach <w...@tuxedocomputers.com> > Signed-off-by: Andri Yngvason <an...@yngvason.is> > Signed-off-by: Marius Vlad <marius.v...@collabora.com> > --- > drivers/gpu/drm/drm_atomic_helper.c | 5 + > drivers/gpu/drm/drm_atomic_uapi.c | 4 + > drivers/gpu/drm/drm_connector.c | 177 ++++++++++++++++++++++++++++ > include/drm/drm_connector.h | 54 ++++++++- > 4 files changed, 235 insertions(+), 5 deletions(-) > -- With best wishes Dmitry
