From: Dmitry Osipenko <digetx@gmail.com>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
dri-devel@lists.freedesktop.org
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Russell King <linux@armlinux.org.uk>,
linux-renesas-soc@vger.kernel.org,
Ben Skeggs <bskeggs@redhat.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Alexandru Gheorghe <Alexandru_Gheorghe@mentor.com>,
linux-media@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH/RFC 0/4] Implement standard color keying properties
Date: Wed, 25 Apr 2018 22:27:41 +0300 [thread overview]
Message-ID: <fc704d59-eee5-c3cd-090d-b5cdd71186be@gmail.com> (raw)
In-Reply-To: <20171217001724.1348-1-laurent.pinchart+renesas@ideasonboard.com>
Hello Laurent,
On 17.12.2017 03:17, Laurent Pinchart wrote:
> Hello,
>
> This patch series is an attempt at implementing standard properties for color
> keying support in the KMS API.
I was looking at implementing colorkey support for NVIDIA Tegra (older Tegra's
in particular) and Daniel Vetter suggested that colorkey should be implemented
as a generic plane property, instead of a custom one that I had in the patch
[0]. I've applied your RFC patch and replaced custom property with the generic,
it works well.
Very likely that all HW should be capable of making pixel completely transparent
when it matches a specified color, that could be one of common modes. Though
there could be limitations, like Tegra's aren't able to do blending-over of
planes if colorkey'ing is enabled. The 'colorkey.mode' property allows driver to
expose both common properties and a custom ones. In case of Tegra we could
implement a common property such that atomic commit will be rejected if planes
blending mode aren't compatible with the enabled colorkey'ing, and have a custom
property for a custom HW-aware application that won't be rejected (for example
Opentegra's Xv extension). The common modes could be derived later, once generic
property will get more usage by a variety of drivers. For now I don't see any
issues with your approach and hope to see this series applied in upstream to get
use of them, please continue your effort.
[0] https://patchwork.kernel.org/patch/10342849/
prev parent reply other threads:[~2018-04-25 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 0:17 [PATCH/RFC 0/4] Implement standard color keying properties Laurent Pinchart
2017-12-17 0:17 ` [PATCH/RFC 1/4] drm: Add colorkey properties Laurent Pinchart
2017-12-19 9:00 ` Neil Armstrong
2017-12-19 13:14 ` Laurent Pinchart
2018-01-25 10:55 ` Maxime Ripard
2018-04-25 19:33 ` Dmitry Osipenko
2018-04-26 13:27 ` Ville Syrjälä
2017-12-17 0:17 ` [PATCH/RFC 2/4] drm: rcar-du: Use standard " Laurent Pinchart
2017-12-17 0:17 ` [PATCH/RFC 3/4] v4l: vsp1: Add support for colorkey alpha blending Laurent Pinchart
2017-12-17 0:17 ` [PATCH/RFC 4/4] drm: rcar-du: Add support for color keying on Gen3 Laurent Pinchart
2018-01-25 10:57 ` Maxime Ripard
2018-04-25 19:27 ` Dmitry Osipenko [this message]
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=fc704d59-eee5-c3cd-090d-b5cdd71186be@gmail.com \
--to=digetx@gmail.com \
--cc=Alexandru_Gheorghe@mentor.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rodrigo.vivi@intel.com \
--cc=thellstrom@vmware.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