From: Mika Kahola <mika.kahola@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: petri.latvala@intel.com
Subject: [igt-dev] [PATCH i-g-t 0/2] tests/kms_concurrent: Calculate maximum number of planes to meet bandwidth requirement
Date: Tue, 31 Mar 2020 14:58:22 +0300 [thread overview]
Message-ID: <20200331115824.2481-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.
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-03-31 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 11:58 Mika Kahola [this message]
2020-03-31 11:58 ` [igt-dev] [PATCH i-g-t 1/2] Revert "tests/kms_concurrent: Test maximum number of planes supported by the platform" Mika Kahola
2020-03-31 11:58 ` [igt-dev] [PATCH i-g-t 2/2] tests/kms_concurrent: Use maximum number of planes that display/platform combination supports Mika Kahola
2020-04-01 6:51 ` Petri Latvala
2020-04-01 2:17 ` [igt-dev] ✗ Fi.CI.BUILD: failure for tests/kms_concurrent: Calculate maximum number of planes to meet bandwidth requirement Patchwork
2020-04-01 2:24 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2020-04-01 6:16 ` [igt-dev] ✗ Fi.CI.BUILD: failure for tests/kms_concurrent: Calculate maximum number of planes to meet bandwidth requirement (rev2) Patchwork
2020-04-01 6:26 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
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=20200331115824.2481-1-mika.kahola@intel.com \
--to=mika.kahola@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--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