All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilia Mirkin <imirkin@alum.mit.edu>
To: Daniel Stone <daniel@fooishbar.org>
Cc: David Airlie <airlied@linux.ie>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 25/25] drm/armada: add iturbt_709 plane property to control YUV colorspace
Date: Wed, 13 Dec 2017 11:12:18 -0500	[thread overview]
Message-ID: <CAKb7Uvizo039piL4BD_NYkL5zZTtTLr_=hrHGaf8uzFe_LFirw@mail.gmail.com> (raw)
In-Reply-To: <CAPj87rO=-oRAnrP7yrrsahyL6=3rjVnv_zwcb-Rj+MYXSH8=bQ@mail.gmail.com>

On Wed, Dec 13, 2017 at 10:41 AM, Daniel Stone <daniel@fooishbar.org> wrote:
> Hi Russell,
>
> On 8 December 2017 at 12:31, Russell King <rmk+kernel@armlinux.org.uk> wrote:
>> Add the defacto-standard "iturbt_709" property to the overlay plane to
>> control the YUV to RGB colorspace conversion.  This is mutually
>> exclusive with the CSC_YUV CRTC property - the last property to be set
>> determines the resulting colorspace conversion.
>
> I haven't seen this in other drivers - is it a 'defacto standard'? I

xf86-video-nv supported it, and I added it to nouveau as well when I
ported YUV plane support. Some video players use the Xv property when
available.

https://cgit.freedesktop.org/xorg/driver/xf86-video-nv/tree/src/nv_video.c#n128
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/nouveau/dispnv04/overlay.c?h=v4.15-rc3#n316

Cheers,

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

  parent reply	other threads:[~2017-12-13 16:12 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 12:13 [PATCH v2 0/5] Armada DRM fixes Russell King - ARM Linux
2017-12-08 12:14 ` [PATCH 1/5] drm/armada: fix leak of crtc structure Russell King
2017-12-08 12:14 ` [PATCH 2/5] drm/armada: fix SRAM powerdown Russell King
2017-12-08 12:14 ` [PATCH 3/5] drm/armada: fix UV swap code Russell King
2017-12-08 12:14 ` [PATCH 4/5] drm/armada: improve efficiency of armada_drm_plane_calc_addrs() Russell King
2017-12-08 12:14 ` [PATCH 5/5] drm/armada: fix YUV planar format framebuffer offsets Russell King
2017-12-08 12:27 ` [PATCH 00/25] Armada DRM development for 4.16 Russell King - ARM Linux
2017-12-08 12:29   ` [PATCH 01/25] drm/armada: remove armada_drm_plane_work_cancel() return value Russell King
2017-12-08 12:29   ` [PATCH 02/25] drm/armada: add a common frame work allocator Russell King
2017-12-08 12:29   ` [PATCH 03/25] drm/armada: store plane in armada_plane_work Russell King
2017-12-08 12:29   ` [PATCH 04/25] drm/armada: add work cancel callback Russell King
2017-12-08 12:29   ` [PATCH 05/25] drm/armada: wait and cancel any pending frame work at disable Russell King
2017-12-08 12:29   ` [PATCH 06/25] drm/armada: allow the primary plane to be disabled Russell King
2017-12-08 12:29   ` [PATCH 07/25] drm/armada: clean up armada_drm_crtc_plane_disable() Russell King
2017-12-08 12:29   ` [PATCH 08/25] drm/armada: clear plane enable bit when disabling Russell King
2017-12-08 12:29   ` [PATCH 09/25] drm/armada: move overlay plane work out from under spinlock Russell King
2017-12-08 12:29   ` [PATCH 10/25] drm/armada: move fb retirement into armada_plane_work Russell King
2017-12-08 12:29   ` [PATCH 11/25] drm/armada: move event sending " Russell King
2017-12-08 12:29   ` [PATCH 12/25] drm/armada: move regs " Russell King
2017-12-08 12:30   ` [PATCH 13/25] drm/armada: move writes of LCD_SPU_SRAM_PARA1 under lock Russell King
2017-12-08 12:30   ` [PATCH 14/25] drm/armada: only enable HSMOOTH if scaling horizontally Russell King
2017-12-08 12:30   ` [PATCH 15/25] drm/armada: use drm_plane_helper_check_state() Russell King
2017-12-08 12:30   ` [PATCH 16/25] drm/armada: allow armada_drm_plane_work_queue() to silently fail Russell King
2017-12-08 12:30   ` [PATCH 17/25] drm/armada: avoid work allocation Russell King
2017-12-08 12:30   ` [PATCH 18/25] drm/armada: disable planes at next blanking period Russell King
2017-12-08 12:30   ` [PATCH 19/25] drm/armada: re-organise overlay register update generation Russell King
2017-12-08 12:30   ` [PATCH 20/25] drm/armada: move overlay plane " Russell King
2017-12-08 12:30   ` [PATCH 21/25] drm/armada: wait for previous work when moving overlay window Russell King
2017-12-08 12:30   ` [PATCH 22/25] drm/armada: extract register generation from armada_drm_primary_set() Russell King
2017-12-08 12:30   ` [PATCH 23/25] drm/armada: implement primary plane update Russell King
2017-12-08 12:31   ` [PATCH 24/25] drm/armada: expand overlay trace entry Russell King
2017-12-08 12:31   ` [PATCH 25/25] drm/armada: add iturbt_709 plane property to control YUV colorspace Russell King
2017-12-11 20:54     ` Daniel Vetter
2017-12-11 22:17       ` Russell King - ARM Linux
2017-12-13 15:02     ` Ville Syrjälä
2017-12-13 15:41     ` Daniel Stone
2017-12-13 16:07       ` Russell King - ARM Linux
2017-12-13 16:12       ` Ilia Mirkin [this message]
2017-12-13 16:22         ` Ville Syrjälä
2018-01-01 12:17           ` Russell King - ARM Linux
2018-07-20 11:39             ` Russell King - ARM Linux
2018-07-20 12:26               ` 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='CAKb7Uvizo039piL4BD_NYkL5zZTtTLr_=hrHGaf8uzFe_LFirw@mail.gmail.com' \
    --to=imirkin@alum.mit.edu \
    --cc=airlied@linux.ie \
    --cc=daniel@fooishbar.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=rmk+kernel@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.