From: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
To: Brian Starkey <brian.starkey@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Daniel Vetter <daniel@ffwll.ch>,
Haneen Mohammed <hamohammed.sa@gmail.com>,
Simon Ser <contact@emersion.fr>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH V3 0/5] drm/vkms: Introduces writeback support
Date: Tue, 25 Jun 2019 22:35:30 -0300 [thread overview]
Message-ID: <cover.1561491964.git.rodrigosiqueiramelo@gmail.com> (raw)
This is the V3 version of a series that introduces the writeback support
to vkms. As a result of the previous review, this patchset can be seen
in three parts: make vkms able to support multiple connector, pre-work
for vkms, and the vkms implementation. Follows the details:
* First part: The first patch of this series is a fix that enables vkms to
accept new connectors, such as writeback connector.
* Second part: The second part of this patchset starts on patch 02 and
finish on patch 04; basically it is a pre-work that aims to make vkms
composer operations a little bit more generic. These patches update the
CRC files and function to make it work as a composer; it also
centralizes the vkms framebuffer operations. Additionally, these changes
enable the composer to use the writeback framebuffer instead of creating
a copy.
* Third part: The final patch enables the support for writeback in vkms.
With this patchset, vkms can successfully pass all the kms_writeback
tests from IGT.
Note: Most of the changes in the V3 was suggested by Daniel Vetter as
can be seen at the link
https://patchwork.freedesktop.org/patch/311844/?series=61738&rev=2
Note: This patchset depends on Daniel's rework of CRC, see it at
https://patchwork.freedesktop.org/series/61737/
Rodrigo Siqueira (5):
drm/vkms: Avoid assigning 0 for possible_crtc
drm/vkms: Rename vkms_crc.c into vkms_composer.c
drm/vkms: Decouple crc operations from composer
drm/vkms: Compute CRC without change input data
drm/vkms: Add support for writeback
drivers/gpu/drm/vkms/Makefile | 9 +-
.../drm/vkms/{vkms_crc.c => vkms_composer.c} | 174 ++++++++++--------
drivers/gpu/drm/vkms/vkms_crtc.c | 30 +--
drivers/gpu/drm/vkms/vkms_drv.c | 10 +-
drivers/gpu/drm/vkms/vkms_drv.h | 40 ++--
drivers/gpu/drm/vkms/vkms_output.c | 16 +-
drivers/gpu/drm/vkms/vkms_plane.c | 40 ++--
drivers/gpu/drm/vkms/vkms_writeback.c | 141 ++++++++++++++
8 files changed, 331 insertions(+), 129 deletions(-)
rename drivers/gpu/drm/vkms/{vkms_crc.c => vkms_composer.c} (51%)
create mode 100644 drivers/gpu/drm/vkms/vkms_writeback.c
--
2.21.0
--
Rodrigo Siqueira
https://siqueira.tech
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-06-26 1:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 1:35 Rodrigo Siqueira [this message]
2019-06-26 1:36 ` [PATCH V3 1/5] drm/vkms: Avoid assigning 0 for possible_crtc Rodrigo Siqueira
2019-07-11 8:06 ` Daniel Vetter
2019-06-26 1:37 ` [PATCH V3 2/5] drm/vkms: Rename vkms_crc.c into vkms_composer.c Rodrigo Siqueira
2019-07-11 8:10 ` Daniel Vetter
2019-06-26 1:37 ` [PATCH V3 3/5] drm/vkms: Decouple crc operations from composer Rodrigo Siqueira
2019-07-11 8:19 ` Daniel Vetter
2019-07-11 8:23 ` Simon Ser
2019-06-26 1:38 ` [PATCH V3 4/5] drm/vkms: Compute CRC without change input data Rodrigo Siqueira
2019-07-09 10:05 ` Vasilev, Oleg
2019-07-11 8:21 ` Daniel Vetter
2019-07-11 8:28 ` Simon Ser
2019-07-11 9:00 ` Daniel Vetter
2019-07-12 3:14 ` Rodrigo Siqueira
2019-07-16 8:37 ` Daniel Vetter
2019-07-17 2:30 ` Rodrigo Siqueira
2019-06-26 1:39 ` [PATCH V3 5/5] drm/vkms: Add support for writeback Rodrigo Siqueira
2019-07-11 8:34 ` Daniel Vetter
2019-07-12 3:37 ` Rodrigo Siqueira
2019-07-16 8:40 ` Daniel Vetter
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=cover.1561491964.git.rodrigosiqueiramelo@gmail.com \
--to=rodrigosiqueiramelo@gmail.com \
--cc=brian.starkey@arm.com \
--cc=contact@emersion.fr \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.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