From: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
To: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
nd <nd@arm.com>
Cc: Petri Latvala <petri.latvala@intel.com>,
Simon Ser <contact@emersion.fr>,
Liviu Dudau <Liviu.Dudau@arm.com>,
Maxime Ripard <maxime@cerno.tech>,
Daniel Vetter <daniel@ffwll.ch>,
Brian Starkey <Brian.Starkey@arm.com>
Subject: [igt-dev] [PATCH i-g-t v8 0/4] Add support for testing writeback connectors
Date: Thu, 23 Apr 2020 21:26:01 -0400 [thread overview]
Message-ID: <20200424012605.2279679-1-rodrigosiqueiramelo@gmail.com> (raw)
Hi,
A couple of months ago, I updated and re-submitted a patchset made by
Brian Starkey and Liviu Dudau for adding a writeback connectors test to
IGT. It is important to highlight that DRM already have writeback
connectors support, which is a way to expose in DRM the hardware
functionality from display engines that allows writing back into memory
the result of the DE's composition of supported planes.
After I resubmitted the patchset, Simon Ser provides a long and detailed
review for all of the patches (thanks Simon). Additionally, Maxime
Ripard tested the previous series in an ARM32 architecture and provided
his feedback for making this patchset portable (thanks Maxime). I
finally had time to go through all the details and prepare this new
version. Follows some notes:
1. Patchset author
Brian Starkey is the original author of this patchset, and I'm just
trying to upstream his changes. Note that during this patch submission,
the mail server from google going to overwrite Brian's mail by mine;
this happens on the mail server side for avoiding malicious users to
send emails as someone else. Note that I could spend time figuring out
how to fix it, but I think this is not worth since I can fix it during
the merge process (if it got accepted).
2. Drop the clone commits from the series
After Simon's review, we decided to drop the last two patches of the
original series since it was related to cloning output, and VKMS does
not support it yet. However, after we finish with this series, I can try
to take a look at this feature or maybe propose it as a GSoC/Outreachy
project.
Most of the changes happened in the second patch.
3. Cross-platform improvements
Thanks
Brian Starkey (4):
lib/igt_kms: Add writeback support
kms_writeback: Add initial writeback tests
lib: Add function to hash a framebuffer
kms_writeback: Add writeback-check-output
lib/igt_fb.c | 63 ++++++
lib/igt_fb.h | 2 +
lib/igt_kms.c | 57 ++++++
lib/igt_kms.h | 6 +
tests/Makefile.sources | 1 +
tests/kms_writeback.c | 443 +++++++++++++++++++++++++++++++++++++++++
tests/meson.build | 1 +
7 files changed, 573 insertions(+)
create mode 100644 tests/kms_writeback.c
--
2.26.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-04-24 1:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 1:26 Rodrigo Siqueira [this message]
2020-04-24 1:26 ` [igt-dev] [PATCH i-g-t v8 1/4] lib/igt_kms: Add writeback support Rodrigo Siqueira
2020-04-24 1:26 ` [igt-dev] [PATCH i-g-t v8 2/4] kms_writeback: Add initial writeback tests Rodrigo Siqueira
2020-04-24 1:26 ` [igt-dev] [PATCH i-g-t v8 3/4] lib: Add function to hash a framebuffer Rodrigo Siqueira
2020-04-24 1:26 ` [igt-dev] [PATCH i-g-t v8 4/4] kms_writeback: Add writeback-check-output Rodrigo Siqueira
2020-04-24 1:51 ` [igt-dev] ✗ GitLab.Pipeline: failure for Add support for testing writeback connectors (rev2) Patchwork
2020-05-04 11:56 ` Arkadiusz Hiler
2020-05-06 22:56 ` Rodrigo Siqueira
2020-04-24 2:02 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-04-24 4:39 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-04-29 15:37 ` [Intel-gfx] [PATCH i-g-t v8 0/4] Add support for testing writeback connectors Maxime Ripard
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=20200424012605.2279679-1-rodrigosiqueiramelo@gmail.com \
--to=rodrigosiqueiramelo@gmail.com \
--cc=Brian.Starkey@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=contact@emersion.fr \
--cc=daniel@ffwll.ch \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime@cerno.tech \
--cc=nd@arm.com \
--cc=petri.latvala@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