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: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH V2 0/5] drm/vkms: Introduces writeback support
Date: Mon, 17 Jun 2019 23:41:55 -0300 [thread overview]
Message-ID: <cover.1560820888.git.rodrigosiqueiramelo@gmail.com> (raw)
This patchset introduces the writeback support to vkms. As a pre-work,
the first set of patches separates part of the code inside vkms_crc to a
new file named vkms_composer; this change allows that other parts of the
vkms take advantage of composing functions. Next, there's a patch that
enables the virtual encoder to be compatible with the crtc when we have
multiple encoders. The final patch adds the required implementation to
enable writeback in the vkms. With this patchset, vkms can successfully
pass all the kms_writeback tests from IGT.
Note: This patchset depends on Daniel's rework of CRC, see it at
https://patchwork.freedesktop.org/series/61737/
Rodrigo Siqueira (5):
drm/vkms: Move functions from vkms_crc to vkms_composer
drm/vkms: Rename crc_enabled to composer_enabled
drm/vkms: Rename vkms_crc_data to vkms_data
drm/vkms: Use index instead of 0 in possible crtc
drm/vkms: Add support for writeback
drivers/gpu/drm/vkms/Makefile | 10 +-
drivers/gpu/drm/vkms/vkms_composer.c | 69 +++++++++++
drivers/gpu/drm/vkms/vkms_composer.h | 12 ++
drivers/gpu/drm/vkms/vkms_crc.c | 81 ++-----------
drivers/gpu/drm/vkms/vkms_crtc.c | 2 +-
drivers/gpu/drm/vkms/vkms_drv.c | 9 +-
drivers/gpu/drm/vkms/vkms_drv.h | 18 ++-
drivers/gpu/drm/vkms/vkms_output.c | 12 +-
drivers/gpu/drm/vkms/vkms_plane.c | 40 +++----
drivers/gpu/drm/vkms/vkms_writeback.c | 166 ++++++++++++++++++++++++++
10 files changed, 315 insertions(+), 104 deletions(-)
create mode 100644 drivers/gpu/drm/vkms/vkms_composer.c
create mode 100644 drivers/gpu/drm/vkms/vkms_composer.h
create mode 100644 drivers/gpu/drm/vkms/vkms_writeback.c
--
2.21.0
next reply other threads:[~2019-06-18 2:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 2:41 Rodrigo Siqueira [this message]
2019-06-18 2:42 ` [PATCH V2 1/5] drm/vkms: Move functions from vkms_crc to vkms_composer Rodrigo Siqueira
2019-06-18 9:27 ` Daniel Vetter
2019-06-18 2:43 ` [PATCH V2 2/5] drm/vkms: Rename crc_enabled to composer_enabled Rodrigo Siqueira
2019-06-18 2:45 ` [PATCH V2 3/5] drm/vkms: Rename vkms_crc_data to vkms_data Rodrigo Siqueira
2019-06-18 2:45 ` [PATCH V2 4/5] drm/vkms: Use index instead of 0 in possible crtc Rodrigo Siqueira
2019-06-18 7:56 ` Simon Ser
2019-06-18 11:09 ` Daniel Vetter
2019-06-18 9:29 ` Daniel Vetter
2019-06-18 2:45 ` [PATCH V2 5/5] drm/vkms: Add support for writeback Rodrigo Siqueira
2019-06-18 9:33 ` Daniel Vetter
2019-06-18 22:10 ` Rodrigo Siqueira
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.1560820888.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