public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	dri-devel@lists.freedesktop.org,
	Harry Wentland <harry.wentland@amd.com>,
	Ilia Mirkin <imirkin@alum.mit.edu>
Subject: Re: [PATCH 0/8] drm: Add COLOR_ENCODING and COLOR_RANGE plane properties
Date: Tue, 20 Feb 2018 15:42:32 +0200	[thread overview]
Message-ID: <20180220134232.GC5453@intel.com> (raw)
In-Reply-To: <20180220112659.GM22199@phenom.ffwll.local>

On Tue, Feb 20, 2018 at 12:26:59PM +0100, Daniel Vetter wrote:
> On Wed, Feb 14, 2018 at 09:23:19PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > Here's a refresh of Jyri's COLOR_ENCODING and COLOR_RANGE properties,
> > and the i915 implementation I did on top. I tossed in a few core
> > updates as well: plane state dump, and the BT.2020 constant luminance
> > variant.
> > 
> > Apparently nouveau is already exposing a "iturbt_709" bool property
> > which allows one to choose between BT.601 and BT.709 encodings, but
> > given that we want at least BT.2020 in addition I don't think that
> > property is good enough. Trying to implement it, and somehow extend
> > it beyond BT.601 vs. BT.709 seems like wasted effort. Hence I think
> > we should just ignore it and move on.
> 
> I discussed the nouveau situation with Illia, and apparently there's not
> yet any userspace using it.

Hmm. Yeah, looks like the Xv port attribute is there in nv/nouveau ddx
but it's not implemented via the kms property.

> Which means we could still quickly rename it,
> before Illia adds the ddx support. Would be great if someone could do that
> :-)
> 
> Cheers, Daniel
> 
> > 
> > My userspace implementation in the form of intel ddx
> > XV_COLORSPACE attribute:
> > https://patchwork.freedesktop.org/patch/204696/
> > 
> > Cc: Harry Wentland <harry.wentland@amd.com>
> > Cc: Daniel Vetter <daniel@ffwll.ch>
> > Cc: Daniel Stone <daniel@fooishbar.org>
> > Cc: Russell King - ARM Linux <linux@armlinux.org.uk>
> > Cc: Ilia Mirkin <imirkin@alum.mit.edu>
> > Cc: Hans Verkuil <hverkuil@xs4all.nl>
> > Cc: Uma Shankar <uma.shankar@intel.com>
> > Cc: Shashank Sharma <shashank.sharma@intel.com>
> > 
> > Jyri Sarha (1):
> >   drm: Add optional COLOR_ENCODING and COLOR_RANGE properties to
> >     drm_plane
> > 
> > Ville Syrjälä (7):
> >   drm: Add BT.2020 constant luminance enum value for the COLOR_ENCODING
> >     property
> >   drm/atomic: Include color encoding/range in plane state dump
> >   drm/i915: Correctly handle limited range YCbCr data on VLV/CHV
> >   drm/i915: Fix plane YCbCr->RGB conversion for GLK
> >   drm/i915: Add support for the YCbCr COLOR_ENCODING property
> >   drm/i915: Change the COLOR_ENCODING prop default value to BT.709
> >   drm/i915: Add support for the YCbCr COLOR_RANGE property
> > 
> >  drivers/gpu/drm/drm_atomic.c         |  12 ++++
> >  drivers/gpu/drm/drm_color_mgmt.c     | 108 ++++++++++++++++++++++++++++
> >  drivers/gpu/drm/drm_crtc_internal.h  |   2 +
> >  drivers/gpu/drm/i915/i915_reg.h      |  24 ++++++-
> >  drivers/gpu/drm/i915/intel_display.c |  25 +++++++
> >  drivers/gpu/drm/i915/intel_drv.h     |   2 +
> >  drivers/gpu/drm/i915/intel_sprite.c  | 134 ++++++++++++++++++++++++++++-------
> >  include/drm/drm_color_mgmt.h         |  20 ++++++
> >  include/drm/drm_plane.h              |   8 +++
> >  9 files changed, 309 insertions(+), 26 deletions(-)
> > 
> > -- 
> > 2.13.6
> > 
> 
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-02-20 13:42 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 19:23 [PATCH 0/8] drm: Add COLOR_ENCODING and COLOR_RANGE plane properties Ville Syrjala
2018-02-14 19:23 ` [PATCH 1/8] drm: Add optional COLOR_ENCODING and COLOR_RANGE properties to drm_plane Ville Syrjala
2018-02-19 15:04   ` Daniel Vetter
2018-02-19 20:19     ` Ville Syrjälä
2018-02-19 20:38       ` Jyri Sarha
2018-02-19 22:38         ` Daniel Vetter
2018-02-19 20:28   ` [PATCH v2 " Ville Syrjala
2018-02-20 11:24     ` Daniel Vetter
2018-11-30 13:08     ` [v2, " Christoph Manszewski
2018-11-30 13:25       ` Ville Syrjälä
2018-11-30 14:20         ` Andrzej Hajda
2018-11-30 14:29           ` Ville Syrjälä
2018-11-30 14:48             ` Hans Verkuil
2018-11-30 15:16               ` Ville Syrjälä
2018-11-30 15:34                 ` Hans Verkuil
2018-11-30 16:22                   ` Brian Starkey
2018-12-03 11:23               ` Andrzej Hajda
2018-12-03 11:52                 ` Hans Verkuil
2018-12-03 12:51                   ` Andrzej Hajda
2018-11-30 14:40           ` Hans Verkuil
2018-02-14 19:23 ` [PATCH 2/8] drm: Add BT.2020 constant luminance enum value for the COLOR_ENCODING property Ville Syrjala
2018-03-02 12:40   ` Ville Syrjälä
2018-02-14 19:23 ` [PATCH 3/8] drm/atomic: Include color encoding/range in plane state dump Ville Syrjala
2018-02-19 15:08   ` Daniel Vetter
2018-02-19 20:28   ` [PATCH v2 " Ville Syrjala
2018-02-20 11:25     ` Daniel Vetter
2018-02-20 15:57     ` Harry Wentland
2018-02-14 19:23 ` [PATCH 4/8] drm/i915: Correctly handle limited range YCbCr data on VLV/CHV Ville Syrjala
2018-02-14 19:23 ` [PATCH 5/8] drm/i915: Fix plane YCbCr->RGB conversion for GLK Ville Syrjala
2018-02-28 20:43   ` Imre Deak
2018-02-14 19:23 ` [PATCH 6/8] drm/i915: Add support for the YCbCr COLOR_ENCODING property Ville Syrjala
2018-02-14 19:23 ` [PATCH 7/8] drm/i915: Change the COLOR_ENCODING prop default value to BT.709 Ville Syrjala
2018-02-14 19:23 ` [PATCH 8/8] drm/i915: Add support for the YCbCr COLOR_RANGE property Ville Syrjala
2018-02-14 20:53 ` ✗ Fi.CI.CHECKPATCH: warning for drm: Add COLOR_ENCODING and COLOR_RANGE plane properties Patchwork
2018-02-14 20:56 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-02-14 21:09 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-15  5:34 ` ✓ Fi.CI.IGT: " Patchwork
2018-02-19 15:00 ` [PATCH 0/8] " Daniel Vetter
2018-02-19 15:09 ` Daniel Vetter
2018-02-19 15:52   ` Ville Syrjälä
2018-02-19 20:41 ` ✗ Fi.CI.CHECKPATCH: warning for drm: Add COLOR_ENCODING and COLOR_RANGE plane properties (rev3) Patchwork
2018-02-19 20:43 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-02-19 20:59 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-20  0:20 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-02-20 11:26 ` [PATCH 0/8] drm: Add COLOR_ENCODING and COLOR_RANGE plane properties Daniel Vetter
2018-02-20 13:42   ` Ville Syrjälä [this message]
2018-03-02 13:06 ` Ville Syrjälä

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=20180220134232.GC5453@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=hverkuil@xs4all.nl \
    --cc=imirkin@alum.mit.edu \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux@armlinux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox