From: Mika Kahola <mika.kahola@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: juhapekka.heikkila@intel.com, petri.latvala@intel.com
Subject: [igt-dev] [PATCH i-g-t v2 0/2] tests/kms_concurrent: Calculate maximum number of planes to meet bandwidth requirement
Date: Wed, 1 Apr 2020 09:54:21 +0300 [thread overview]
Message-ID: <20200401065423.29345-1-mika.kahola@intel.com> (raw)
The first patch reverts a commit that caused regression on HSW pipe B/C tests.
The second patch proposes a different approach, compared to reverted patch,
to calculate maximum number of planes that still meet the bandwidth limitation.
v2: Fix CI build failure (CI)
Mika Kahola (2):
Revert "tests/kms_concurrent: Test maximum number of planes supported
by the platform"
tests/kms_concurrent: Use maximum number of planes that
display/platform combination supports
tests/kms_concurrent.c | 77 +++++++++++++++++-------------------------
1 file changed, 31 insertions(+), 46 deletions(-)
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-04-01 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 6:54 Mika Kahola [this message]
2020-04-01 6:54 ` [igt-dev] [PATCH i-g-t v2 1/2] Revert "tests/kms_concurrent: Test maximum number of planes supported by the platform" Mika Kahola
2020-04-07 11:00 ` Petri Latvala
2020-04-01 6:54 ` [igt-dev] [PATCH i-g-t v2 2/2] tests/kms_concurrent: Use maximum number of planes that display/platform combination supports Mika Kahola
2020-04-08 16:41 ` Lisovskiy, Stanislav
2020-04-09 7:18 ` Kahola, Mika
2020-04-01 7:27 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_concurrent: Calculate maximum number of planes to meet bandwidth requirement (rev3) Patchwork
2020-04-01 19:05 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2020-04-02 6:02 ` Kahola, Mika
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=20200401065423.29345-1-mika.kahola@intel.com \
--to=mika.kahola@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@intel.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