From: Melissa Wen <melissa.srw@gmail.com>
To: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
Cc: daniels@collabora.com, Liviu Dudau <liviu.dudau@arm.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Emil Velikov <emil.l.velikov@gmail.com>,
Leandro Ribeiro <leandro.ribeiro@collabora.com>
Subject: Re: [PATCH v5 0/3] drm/vkms: Introduces writeback support
Date: Tue, 25 Aug 2020 13:02:06 -0300 [thread overview]
Message-ID: <20200825160206.jpdxrdbswaogayzu@smtp.gmail.com> (raw)
In-Reply-To: <20200825023142.2561220-1-rodrigosiqueiramelo@gmail.com>
Hi Rodrigo,
Nice work!
I tested this on the kms_writeback set of subtests and works fine.
I have also checked it on the other IGT tests that I usually uses:
- kms_cursor_crc/cursor-alpha-transparent was affected by a small
problem in the bitmap_clear of the get_pixel_from_buffer function,
that I pointed out inline. Please, check it.
- kms_flip and kms_pipe_crc_basic works as expected (was not affected).
Best regards,
Melissa Wen
On 08/24, Rodrigo Siqueira wrote:
> This is the V5 version of a series that introduces the writeback support
> to VKMS. The first two patches of this series are a pre-work for the
> latest patch that adds the writeback connector, this patchset can be seen
> in two parts:
>
> * A pre-work that aims to make vkms composer operations a little bit more
> generic; these patches try to centralize the vkms framebuffer operations.
> * The final patch enables the support for writeback in vkms.
>
> In the previous review, Emil suggested multiple changes in the series. I
> tried to apply most of the recommendations except for some suggestions
> which I was not able to incorporate due to compilation issues, or other
> suggestions that may complicate this series review. I left some changes
> for future patches for keeping this patchset simple with the hope of
> landing this feature soon in order to support VKMS user's requirements.
> Emil, let me know if you want me to change any other thing.
>
> It is important to highlight that from the previous series to the
> current version of this patchset we had some changes in the VKMS that
> made it unstable. In particular, our previous writeback series stopped
> working properly due to changes in our commit tail. Thanks to Melissa
> working in the instability issue and her latest fixes to VKMS, I finally
> could update writeback and make it work again. The main update in the
> latest patch is the use of vkms_set_composer when the writeback work
> starts (enable composer) and after the writeback end (disable composer).
>
> Best Regard
>
> Rodrigo Siqueira (3):
> 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 +-
> drivers/gpu/drm/vkms/vkms_composer.c | 102 +++++++++++-------
> drivers/gpu/drm/vkms/vkms_drv.h | 11 +-
> drivers/gpu/drm/vkms/vkms_output.c | 4 +
> drivers/gpu/drm/vkms/vkms_writeback.c | 143 ++++++++++++++++++++++++++
> 5 files changed, 231 insertions(+), 38 deletions(-)
> create mode 100644 drivers/gpu/drm/vkms/vkms_writeback.c
>
> --
> 2.28.0
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-08-25 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 2:31 [PATCH v5 0/3] drm/vkms: Introduces writeback support Rodrigo Siqueira
2020-08-25 2:31 ` [PATCH v5 1/3] drm/vkms: Decouple crc operations from composer Rodrigo Siqueira
2020-08-25 16:12 ` Melissa Wen
2020-08-25 2:31 ` [PATCH v5 2/3] drm/vkms: Compute CRC without change input data Rodrigo Siqueira
2020-08-25 15:42 ` Melissa Wen
2020-08-25 2:31 ` [PATCH v5 3/3] drm/vkms: Add support for writeback Rodrigo Siqueira
2020-08-25 15:45 ` Melissa Wen
2020-08-25 16:10 ` Melissa Wen
2020-08-25 16:02 ` Melissa Wen [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=20200825160206.jpdxrdbswaogayzu@smtp.gmail.com \
--to=melissa.srw@gmail.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=leandro.ribeiro@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=rodrigosiqueiramelo@gmail.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).