From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: "Syrjala, Ville" <ville.syrjala@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>, Adam Jackson <ajax@redhat.com>,
"Lankhorst, Maarten" <maarten.lankhorst@intel.com>
Subject: Re: [RFC 1/3] drm: Add colorspace property
Date: Wed, 26 Sep 2018 12:41:34 +0300 [thread overview]
Message-ID: <20180926094134.GR9144@intel.com> (raw)
In-Reply-To: <5bd98a7e-2d89-b1e2-da34-8cc348c5075f@linux.intel.com>
On Wed, Sep 26, 2018 at 11:08:37AM +0200, Maarten Lankhorst wrote:
> Op 01-08-18 om 16:01 schreef Shankar, Uma:
> >
> >> -----Original Message-----
> >> From: Adam Jackson [mailto:ajax@redhat.com]
> >> Sent: Wednesday, August 1, 2018 1:24 AM
> >> To: Shankar, Uma <uma.shankar@intel.com>; intel-gfx@lists.freedesktop.org;
> >> dri-devel@lists.freedesktop.org
> >> Cc: Syrjala, Ville <ville.syrjala@intel.com>; Lankhorst, Maarten
> >> <maarten.lankhorst@intel.com>
> >> Subject: Re: [RFC 1/3] drm: Add colorspace property
> >>
> >> On Tue, 2018-07-24 at 21:15 +0530, Uma Shankar wrote:
> >>
> >>> --- a/include/uapi/drm/drm_mode.h
> >>> +++ b/include/uapi/drm/drm_mode.h
> >>> @@ -209,6 +209,17 @@
> >>> #define DRM_MODE_CONTENT_PROTECTION_DESIRED 1
> >>> #define DRM_MODE_CONTENT_PROTECTION_ENABLED 2
> >>>
> >>> +enum extended_colorimetry {
> >>> + EXTENDED_COLORIMETRY_XV_YCC_601 = 0,
> >>> + EXTENDED_COLORIMETRY_XV_YCC_709,
> >>> + EXTENDED_COLORIMETRY_S_YCC_601,
> >>> + EXTENDED_COLORIMETRY_ADOBE_YCC_601,
> >>> + EXTENDED_COLORIMETRY_ADOBE_RGB,
> >>> + EXTENDED_COLORIMETRY_BT2020_RGB,
> >>> + EXTENDED_COLORIMETRY_BT2020_YCC,
> >>> + EXTENDED_COLORIMETRY_BT2020_CYCC,
> >>> +};
> >> This doesn't give any way to distinguish "not set" from BT.601, which I'm not sure
> >> I like.
> > This enum gives a list of all possible colorspace which can be set on the sink device.
> > The compositors/userspace can choose one of them, based on the capabilities of sink
> > as well as based on rendering/blending policies which are designed to take advantage
> > of hardware resources available.
> >
> > If you suggest to add something like NO_COLORSPACE_SET = -1, I can add that to this
> > enum list.
> I would add a default, but not sure I would introduce a new enum.
> hdmi_extended_colorimetry is already available.
Yeah, there should be a default entry for "driver automagically picks
something suitable".
I think the enum prop should also be some kind of superset of all
CEA-861 normal+extended colorimetry options and DP MSA+VSC SDP
colorimetry options. The current list seems a bit incomplete to me.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-09-26 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 15:45 [RFC 0/3] Add Colorspace connector property interface Uma Shankar
2018-07-24 15:45 ` [RFC 1/3] drm: Add colorspace property Uma Shankar
2018-07-31 19:54 ` Adam Jackson
2018-08-01 14:01 ` Shankar, Uma
2018-09-26 9:08 ` Maarten Lankhorst
2018-09-26 9:41 ` Ville Syrjälä [this message]
2018-09-27 4:29 ` Shankar, Uma
2018-09-27 13:24 ` Ville Syrjälä
2018-07-24 15:45 ` [RFC 2/3] drm/i915: Attach colorspace property and enable modeset Uma Shankar
2018-07-24 15:45 ` [RFC 3/3] drm/i915: Set colorspace by enabling Infoframe Uma Shankar
2018-09-26 9:10 ` Maarten Lankhorst
2018-09-27 4:31 ` [Intel-gfx] " Shankar, Uma
2018-07-24 16:09 ` ✗ Fi.CI.CHECKPATCH: warning for Add Colorspace connector property interface Patchwork
2018-07-24 16:11 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-24 16:30 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-24 20:29 ` ✓ Fi.CI.IGT: " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180926094134.GR9144@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ajax@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=ville.syrjala@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.