All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jyri Sarha <jsarha@ti.com>
To: dri-devel@lists.freedesktop.org
Cc: Liviu.Dudau@arm.com, Jyri Sarha <jsarha@ti.com>,
	tomi.valkeinen@ti.com, laurent.pinchart@ideasonboard.com
Subject: [PATCH RFC v3] drm: Add properties to control YCbCr to RGB conversion
Date: Mon, 15 May 2017 14:19:08 +0300	[thread overview]
Message-ID: <cover.1494842310.git.jsarha@ti.com> (raw)

Changes since v2 RFC version:
 - Drop the second patch that exposed the raw CSC and preoffset vector
 - Rename YCBCR_ENCODING to COLOR_ENCODING, add YCbCr to enum values instead
 - Split the encoding and used value range to different properties:
   COLOR_ENCODING and COLOR_RANGE

The v2 RFC and the related discussion can be found here:
http://www.spinics.net/lists/dri-devel/msg140329.html

Jyri Sarha (1):
  drm: Add optinal COLOR_ENCODING and COLOR_RANGE properties to
    drm_plane

 drivers/gpu/drm/drm_atomic.c     |  8 ++++
 drivers/gpu/drm/drm_color_mgmt.c | 97 ++++++++++++++++++++++++++++++++++++++++
 drivers/gpu/drm/drm_plane.c      |  6 +++
 include/drm/drm_color_mgmt.h     | 20 +++++++++
 include/drm/drm_plane.h          |  8 ++++
 5 files changed, 139 insertions(+)

-- 
1.9.1

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-05-15 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 11:19 Jyri Sarha [this message]
2017-05-15 11:19 ` [PATCH RFC v3] drm: Add optinal COLOR_ENCODING and COLOR_RANGE properties to drm_plane Jyri Sarha
2017-05-15 12:39   ` Eric Engestrom
2017-05-15 13:34   ` Ville Syrjälä
2017-05-15 14:25     ` Jyri Sarha
2017-05-15 15:19       ` Ville Syrjälä
2017-05-15 20:41         ` Jyri Sarha

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=cover.1494842310.git.jsarha@ti.com \
    --to=jsarha@ti.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=tomi.valkeinen@ti.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.