All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Hans Verkuil <hverkuil@xs4all.nl>, Jyri Sarha <jsarha@ti.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: DRM COLOR_RANGE property
Date: Wed, 4 Jul 2018 14:13:03 +0300	[thread overview]
Message-ID: <20180704111303.GS5565@intel.com> (raw)
In-Reply-To: <20180703161857.GQ17271@n2100.armlinux.org.uk>

On Tue, Jul 03, 2018 at 05:18:57PM +0100, Russell King - ARM Linux wrote:
> Can someone provide a deeper explanation about exactly what this
> property represents please?
> 
> Does this represent the range of YCbCr values _into_ a YCbCr-to-RGB
> conversion (in other words, the range of values in the framebuffer),
> or the expected output range from the conversion?

The color_range/encoding props are about the input. The plane output
is generally full range RGB, but presumably some driver could choose
to use some other internal format as well.

-- 
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-07-04 11:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 16:18 DRM COLOR_RANGE property Russell King - ARM Linux
2018-07-04  8:26 ` Daniel Vetter
2018-07-04  9:05   ` Russell King - ARM Linux
2018-07-04  9:24     ` Daniel Vetter
2018-07-04  9:58       ` Russell King - ARM Linux
2018-07-04 11:06         ` Daniel Vetter
2018-07-05 14:05           ` Ville Syrjälä
2018-07-04 11:30         ` Jyri Sarha
2018-07-04 11:13 ` Ville Syrjälä [this message]
2018-07-04 11:19 ` 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=20180704111303.GS5565@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hverkuil@xs4all.nl \
    --cc=jsarha@ti.com \
    --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 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.