Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [igt-dev] [PATCH i-g-t 0/5] lib/igt_kms: Add for_each_pipe_with_single_output and igt_get_single_output_for_pipe.
@ 2018-03-14 11:20 Maarten Lankhorst
  2018-03-14 11:20 ` [igt-dev] [PATCH i-g-t 1/5] lib/igt_kms: Add functions to get only a single output for a pipe Maarten Lankhorst
                   ` (11 more replies)
  0 siblings, 12 replies; 20+ messages in thread
From: Maarten Lankhorst @ 2018-03-14 11:20 UTC (permalink / raw)
  To: igt-dev

Some tests don't have to be called on all outputs, because they only manipulate the pipe.
For these tests we create 2 helper functions, so we reduce the amount of modesets required.

for_each_pipe_with_single_output is a drop in replacement for for_each_pipe_with_valid_output,
and only iterates 1 output per pipe.

igt_get_single_output_for_pipe returns a valid output for a given pipe, if it can be found.
It can be used in place of a for_each_valid_output_on_pipe loop.

This is just a sample conversion, other tests can be changed when this is accepted..

Maarten Lankhorst (5):
  lib/igt_kms: Add functions to get only a single output for a pipe.
  tests/kms_rmfb: Use for_each_pipe_with_single_output.
  tests/kms_busy: Convert to using igt_get_single_output_for_pipe.
  tests/kms_chv_cursor_fail: Reorder tests, and use
    igt_display_require_output_on_pipe.
  tests/kms_chv_cursor_fail: Handle cleanup better.

 lib/igt_kms.c               | 93 +++++++++++++++++++++++++++++++++++++++++++++
 lib/igt_kms.h               | 26 +++++++++++++
 tests/kms_busy.c            | 38 ++++++++----------
 tests/kms_chv_cursor_fail.c | 90 +++++++++++++++++--------------------------
 tests/kms_rmfb.c            |  8 +---
 5 files changed, 171 insertions(+), 84 deletions(-)

-- 
2.16.2

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 20+ messages in thread

end of thread, other threads:[~2018-03-19 15:07 UTC | newest]

Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-03-14 11:20 [igt-dev] [PATCH i-g-t 0/5] lib/igt_kms: Add for_each_pipe_with_single_output and igt_get_single_output_for_pipe Maarten Lankhorst
2018-03-14 11:20 ` [igt-dev] [PATCH i-g-t 1/5] lib/igt_kms: Add functions to get only a single output for a pipe Maarten Lankhorst
2018-03-14 14:43   ` Ville Syrjälä
2018-03-15 16:58     ` [igt-dev] [PATCH i-g-t] lib/igt_kms: Add functions to get only a single output for a pipe, v2 Maarten Lankhorst
2018-03-14 11:20 ` [igt-dev] [PATCH i-g-t 2/5] tests/kms_rmfb: Use for_each_pipe_with_single_output Maarten Lankhorst
2018-03-14 14:44   ` Ville Syrjälä
2018-03-14 11:20 ` [igt-dev] [PATCH i-g-t 3/5] tests/kms_busy: Convert to using igt_get_single_output_for_pipe Maarten Lankhorst
2018-03-14 14:46   ` Ville Syrjälä
2018-03-16  8:28     ` [igt-dev] [PATCH i-g-t] tests/kms_busy: Convert to using igt_get_single_output_for_pipe, v2 Maarten Lankhorst
2018-03-14 11:20 ` [igt-dev] [PATCH i-g-t 4/5] tests/kms_chv_cursor_fail: Reorder tests, and use igt_display_require_output_on_pipe Maarten Lankhorst
2018-03-14 11:20 ` [igt-dev] [PATCH i-g-t 5/5] tests/kms_chv_cursor_fail: Handle cleanup better Maarten Lankhorst
2018-03-14 14:48   ` Ville Syrjälä
2018-03-19 15:07     ` Maarten Lankhorst
2018-03-14 13:37 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_kms: Add for_each_pipe_with_single_output and igt_get_single_output_for_pipe Patchwork
2018-03-14 17:22 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-03-15 18:31 ` [igt-dev] ✗ Fi.CI.BAT: warning for lib/igt_kms: Add for_each_pipe_with_single_output and igt_get_single_output_for_pipe. (rev2) Patchwork
2018-03-15 19:29 ` Patchwork
2018-03-16  7:29 ` Patchwork
2018-03-16  9:03 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_kms: Add for_each_pipe_with_single_output and igt_get_single_output_for_pipe. (rev3) Patchwork
2018-03-16 10:41 ` [igt-dev] ✗ Fi.CI.IGT: warning " Patchwork

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox