From: Eric Anholt <eric@anholt.net>
To: Alexandru Gheorghe <Alexandru_Gheorghe@mentor.com>,
Alexandru_Gheorghe@mentor.com, laurent.pinchart@ideasonboard.com,
linux-renesas-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
geert@linux-m68k.org, sergei.shtylyov@cogentembedded.com
Subject: Re: [PATCH v2 0/2] rcar-du, vsp1: rcar-gen3: Add support for colorkey alpha blending
Date: Mon, 08 May 2017 09:33:37 -0700 [thread overview]
Message-ID: <8737cf2tr2.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1494152007-30094-1-git-send-email-Alexandru_Gheorghe@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Alexandru Gheorghe <Alexandru_Gheorghe@mentor.com> writes:
> Currently, rcar-du supports colorkeying only for rcar-gen2 and it uses
> some hw capability of the display unit(DU) which is not available on gen3.
> In order to implement colorkeying for gen3 we need to use the colorkey
> capability of the VSPD, hence the need to change both drivers rcar-du and
> vsp1.
>
> This patchset had been developed and tested on top of v4.9/rcar-3.5.1 from
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git
A few questions:
Are other drivers interested in supporting this property? VC4 has the
24-bit RGB colorkey, but I don't see YCBCR support. Should it be
documented in a generic location?
Does your colorkey end up forcing alpha to 1 for the plane when it's not
matched?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-05-08 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 10:13 [PATCH v2 0/2] rcar-du, vsp1: rcar-gen3: Add support for colorkey alpha blending Alexandru Gheorghe
2017-05-07 10:13 ` [PATCH v2 1/2] v4l: vsp1: " Alexandru Gheorghe
2017-06-07 16:56 ` Mauro Carvalho Chehab
2017-05-07 10:13 ` [PATCH v2 2/2] drm: rcar-du: " Alexandru Gheorghe
2017-05-08 16:33 ` Eric Anholt [this message]
2017-05-08 18:29 ` [PATCH v2 0/2] rcar-du, vsp1: rcar-gen3: " Daniel Vetter
2017-05-09 7:12 ` Gheorghe, Alexandru
2017-11-27 11:12 ` Laurent Pinchart
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=8737cf2tr2.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=Alexandru_Gheorghe@mentor.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox