From: Lyude <lyude-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
igt-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [PATCH i-g-t v3 0/5] Add nouveau-crc tests
Date: Fri, 17 Apr 2020 17:10:20 -0400 [thread overview]
Message-ID: <20200417211025.109574-1-lyude@redhat.com> (raw)
From: Lyude Paul <lyude-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Nouveau has finally gotten CRC support, hooray! Well, it's under review
at least:
https://patchwork.freedesktop.org/series/74804/
(it has a cover letter, but nouveau's mailing list configuration has
blocked the email so I'm waiting for a moderator to fix that)
So, this series adds the relevant tests for it since nvidia's CRC
implementation has some rather interesting design choices that needed to
be worked around.
Changes since v2:
* Fix build errors on mips/arm/aarch64
Changes since v1:
* fix documentation errors Petri pointed out
* Fix documentation for igt_require_fd()
* Fix copyright year in tests/nouveau_crc.c
Lyude Paul (5):
lib/igt_core: Fix igt_assert_fd() documentation
lib/igt_core: Add igt_require_fd()
lib/igt_debugfs: Add igt_debugfs_pipe_dir()
lib/igt_kms: Hook up connector dithering prop
tests: Add nouveau-crc tests
lib/drmtest.c | 10 ++
lib/drmtest.h | 2 +
lib/igt_core.h | 16 +-
lib/igt_debugfs.c | 29 ++++
lib/igt_debugfs.h | 1 +
lib/igt_kms.c | 6 +
lib/igt_kms.h | 1 +
tests/meson.build | 1 +
tests/nouveau_crc.c | 397 ++++++++++++++++++++++++++++++++++++++++++++
9 files changed, 461 insertions(+), 2 deletions(-)
create mode 100644 tests/nouveau_crc.c
--
2.25.1
next reply other threads:[~2020-04-17 21:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 21:10 Lyude [this message]
[not found] ` <20200417211025.109574-1-lyude-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-04-17 21:10 ` [PATCH i-g-t v3 1/5] lib/igt_core: Fix igt_assert_fd() documentation Lyude
[not found] ` <20200417211025.109574-2-lyude-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-04-20 9:29 ` [igt-dev] " Petri Latvala
2020-04-17 21:10 ` [PATCH i-g-t v3 2/5] lib/igt_core: Add igt_require_fd() Lyude
[not found] ` <20200417211025.109574-3-lyude-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-04-20 9:29 ` [igt-dev] " Petri Latvala
2020-04-17 21:10 ` [PATCH i-g-t v3 3/5] lib/igt_debugfs: Add igt_debugfs_pipe_dir() Lyude
[not found] ` <20200417211025.109574-4-lyude-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-08-18 21:01 ` [i-g-t, v3, " Jeremy Cline
2020-04-17 21:10 ` [PATCH i-g-t v3 4/5] lib/igt_kms: Hook up connector dithering prop Lyude
[not found] ` <20200417211025.109574-5-lyude-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-08-18 21:18 ` [i-g-t, v3, " Jeremy Cline
2020-04-17 21:10 ` [PATCH i-g-t v3 5/5] tests: Add nouveau-crc tests Lyude
[not found] ` <20200417211025.109574-6-lyude-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-08-18 21:00 ` [PATCH i-g-t v4] " Lyude
[not found] ` <20200818210051.28705-1-lyude-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-09-28 21:36 ` [igt-dev] " Jeremy Cline
2020-09-29 16:13 ` Lyude Paul
[not found] ` <b5673893f45f4bb72a90ca55d45100391a49c8e8.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-09-29 17:42 ` Jeremy Cline
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=20200417211025.109574-1-lyude@redhat.com \
--to=lyude-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=igt-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/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