linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Alexandru Gheorghe <Alexandru_Gheorghe@mentor.com>,
	Russell King <linux@armlinux.org.uk>,
	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 v2 0/2] Implement standard color keying properties for DRM planes
Date: Sat, 26 May 2018 18:56:21 +0300	[thread overview]
Message-ID: <20180526155623.12610-1-digetx@gmail.com> (raw)

Hello, DRM maintainers!

Laurent Pinchart kindly agreed to allow me to pick up his work on
the generic colorkey DRM plane property [0]. I've reworked the original
patch a tad, hopefully making it flexible enough to cover various HW
capabilities.

Changes I've made:

	- Some code clean up and reshuffle.

	- Took into account some the Ville's Syrjälä review comments to [0].

	- The number of common DRM colorkey properties grows from 4 to 9.
	  New properties:
		- colorkey.mask
		- colorkey.format
		- colorkey.inverted-match
		- colorkey.replacement-mask
		- colorkey.replacement-format

	  Renamed properties:
		- colorkey.value -> colorkey.replacement-value

	- colorkey.mode userspace-property ENUM's got a bit more explicit
	  names, like "src" -> "src-match-src-replace".

	- No driver-specific modes / properties allowed, all unsupported
	  features are simply rejected by the drivers.

This patchset includes initial colorkey property implementation for the
older NVIDIA Tegra's.

Please review, thanks.

[0] https://lists.freedesktop.org/archives/dri-devel/2017-December/160510.html

Dmitry Osipenko (2):
  drm: Add generic colorkey properties
  drm/tegra: plane: Implement generic colorkey property for older
    Tegra's

 drivers/gpu/drm/drm_atomic.c  |  36 ++++++
 drivers/gpu/drm/drm_blend.c   | 229 ++++++++++++++++++++++++++++++++++
 drivers/gpu/drm/tegra/dc.c    |  31 +++++
 drivers/gpu/drm/tegra/dc.h    |   7 ++
 drivers/gpu/drm/tegra/plane.c | 147 ++++++++++++++++++++++
 drivers/gpu/drm/tegra/plane.h |   1 +
 include/drm/drm_blend.h       |   3 +
 include/drm/drm_plane.h       |  77 ++++++++++++
 8 files changed, 531 insertions(+)

-- 
2.17.0

             reply	other threads:[~2018-05-26 15:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-26 15:56 Dmitry Osipenko [this message]
2018-05-26 15:56 ` [RFC PATCH v2 1/2] drm: Add generic colorkey properties Dmitry Osipenko
2018-05-26 16:16   ` Laurent Pinchart
2018-05-26 16:18     ` Laurent Pinchart
2018-05-26 16:29       ` Dmitry Osipenko
2018-05-26 16:27     ` Dmitry Osipenko
2018-05-28 13:15   ` Ville Syrjälä
2018-05-28 23:48     ` Dmitry Osipenko
2018-05-28 23:58       ` Dmitry Osipenko
2018-05-29  7:11       ` Ville Syrjälä
2018-06-19 17:40         ` Russell King - ARM Linux
2018-06-20  9:17           ` Daniel Vetter
2018-06-20  9:33             ` Russell King - ARM Linux
2018-06-20 10:10               ` Daniel Vetter
2018-06-20 12:20                 ` Dmitry Osipenko
2018-06-20 12:20           ` Dmitry Osipenko
2018-05-29  7:17   ` Ville Syrjälä
2018-06-02 22:56     ` Dmitry Osipenko
2018-05-26 15:56 ` [RFC PATCH v2 2/2] drm/tegra: plane: Implement generic colorkey property 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=20180526155623.12610-1-digetx@gmail.com \
    --to=digetx@gmail.com \
    --cc=Alexandru_Gheorghe@mentor.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=maxime.ripard@free-electrons.com \
    --cc=narmstrong@baylibre.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).