From: Dmitry Osipenko <digetx@gmail.com>
To: "Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Maxime Ripard" <maxime.ripard@free-electrons.com>,
dri-devel@lists.freedesktop.org,
"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
"Russell King" <linux@armlinux.org.uk>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Ben Skeggs <bskeggs@redhat.com>, Sinclair Yeh <syeh@vmware.com>,
Thomas Hellstrom <thellstrom@vmware.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH v4 0/2] drm: Add generic colorkey plane properties
Date: Tue, 7 Aug 2018 20:22:00 +0300 [thread overview]
Message-ID: <20180807172202.1961-1-digetx@gmail.com> (raw)
Changes in v4:
1) In response to Ville's Syrjälä review comments:
- Added new "colorkey.plane_mask" property that specifies which
planes shall participate in color key matching operation.
- Added short glossary-comment to drm_plane_create_colorkey_properties()
that clarifies 'destination' / 'source' plane terms.
- Returned "colorkey.mask" property that was dropped from v3, looks
like masking is quite common among different HW and hence makes more
sense to have that property by default instead of having additional
color keying modes.
- Changed the color keying mode name to "transparent".
2) In response to Maarten's Lankhorst review comments:
- Added a drm_colorkey_extract_component() helper which is supposed to
commonize color key component value extraction code among DRM drivers.
3) In response to Russell's King review comments:
- The doc-comment to drm_plane_create_colorkey_properties() now
explicitly states that "The converted value shall be *rounded up* to
the nearest value". Hence userspace now knows what to expect when
plane has a 1bpp format.
Please review, thanks.
v3: https://lists.freedesktop.org/archives/dri-devel/2018-June/179057.html
v2: https://lists.freedesktop.org/archives/dri-devel/2018-May/178408.html
v1: https://lists.freedesktop.org/archives/dri-devel/2017-December/160510.html
Dmitry Osipenko (1):
drm/tegra: plane: Add generic colorkey properties for older Tegra's
Laurent Pinchart (1):
drm: Add generic colorkey properties for display planes
drivers/gpu/drm/drm_atomic.c | 20 +++++
drivers/gpu/drm/drm_blend.c | 150 ++++++++++++++++++++++++++++++++
drivers/gpu/drm/tegra/dc.c | 25 ++++++
drivers/gpu/drm/tegra/dc.h | 7 ++
drivers/gpu/drm/tegra/plane.c | 156 ++++++++++++++++++++++++++++++++++
include/drm/drm_blend.h | 3 +
include/drm/drm_plane.h | 91 ++++++++++++++++++++
7 files changed, 452 insertions(+)
--
2.18.0
next reply other threads:[~2018-08-07 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 17:22 Dmitry Osipenko [this message]
2018-08-07 17:22 ` [RFC PATCH v4 1/2] drm: Add generic colorkey properties for display planes Dmitry Osipenko
2018-08-08 8:16 ` Russell King - ARM Linux
2018-08-08 14:30 ` Dmitry Osipenko
2018-08-16 11:42 ` Maarten Lankhorst
2018-09-20 16:04 ` Dmitry Osipenko
2018-08-14 9:48 ` Laurent Pinchart
2018-08-14 10:38 ` Daniel Vetter
2018-09-20 16:46 ` Dmitry Osipenko
2018-09-20 15:10 ` Dmitry Osipenko
2018-08-07 17:22 ` [RFC PATCH v4 2/2] drm/tegra: plane: Add generic colorkey properties for older Tegra's Dmitry Osipenko
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=20180807172202.1961-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--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=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@free-electrons.com \
--cc=narmstrong@baylibre.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=rodrigo.vivi@intel.com \
--cc=syeh@vmware.com \
--cc=thellstrom@vmware.com \
--cc=thierry.reding@gmail.com \
--cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).