From: Jani Nikula <jani.nikula@intel.com>
To: Kunal Joshi <kunal1.joshi@intel.com>, igt-dev@lists.freedesktop.org
Cc: Kunal Joshi <kunal1.joshi@intel.com>
Subject: Re: [PATCH 0/4] add test to validate uhbr/non-uhbr over sst/mst
Date: Mon, 27 Jan 2025 14:31:08 +0200 [thread overview]
Message-ID: <87tt9ka16b.fsf@intel.com> (raw)
In-Reply-To: <20250115073243.2002014-1-kunal1.joshi@intel.com>
On Wed, 15 Jan 2025, Kunal Joshi <kunal1.joshi@intel.com> wrote:
> Add new test validating UHBR and non-UHBR link rates for
> both SST and MST configurations. The series comprises three patches:
>
> 1. tests/intel/kms_joiner_helper:
> - Introduces kms_joiner_helper.c/h for pipe assignments taking care of joiners
> - Moves common joiner-related logic out of kms_joiner.c.
>
> 2. tests/intel/kms_mst_helper:
> - Adds kms_mst_helper.c/h for MST-specific operations.
> - Centralizes code for identifying and assigning MST outputs.
>
> 3. tests/kms_feature_discovery:
> - Implements tests verifying UHBR and non-UHBR link rates with SST and MST.
> - Uses the new helpers for pipe assignments and topology discovery.
AFAICT this adapts to what the driver reports. If the driver never
enables DP SST UHBR, it'll happily pass, and just skip the tests. Am I
right? Is that the kind of testing you want?
BR,
Jani.
> Kunal Joshi (4):
> tests/intel/kms_joiner_helper: helper for joiner-related functions
> tests/intel/kms_mst_helper: Add helper for MST-related functions
> tests/kms_feature_discovery: Add tests for UHBR/non-UHBR over SST/MST
> HAX: DO NOT MERGE
>
> tests/intel-ci/fast-feedback.testlist | 14 ++
> tests/intel-ci/xe-fast-feedback.testlist | 14 ++
> tests/intel/kms_dp_linktrain_fallback.c | 28 +---
> tests/intel/kms_joiner.c | 15 +-
> tests/intel/kms_joiner_helper.c | 179 +++++++++++++++++++++++
> tests/intel/kms_joiner_helper.h | 15 ++
> tests/intel/kms_mst_helper.c | 48 ++++++
> tests/intel/kms_mst_helper.h | 10 ++
> tests/kms_feature_discovery.c | 177 ++++++++++++++++++++++
> tests/meson.build | 6 +
> 10 files changed, 469 insertions(+), 37 deletions(-)
> create mode 100644 tests/intel/kms_joiner_helper.c
> create mode 100644 tests/intel/kms_joiner_helper.h
> create mode 100644 tests/intel/kms_mst_helper.c
> create mode 100644 tests/intel/kms_mst_helper.h
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-01-27 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 7:32 [PATCH 0/4] add test to validate uhbr/non-uhbr over sst/mst Kunal Joshi
2025-01-15 7:32 ` [PATCH 1/4] tests/intel/kms_joiner_helper: helper for joiner-related functions Kunal Joshi
2025-01-15 7:32 ` [PATCH 2/4] tests/intel/kms_mst_helper: Add helper for MST-related functions Kunal Joshi
2025-01-15 7:32 ` [PATCH 3/4] tests/kms_feature_discovery: Add tests for UHBR/non-UHBR over SST/MST Kunal Joshi
2025-01-16 10:24 ` B, Jeevan
2025-01-27 9:49 ` Sharma, Swati2
2025-01-15 7:32 ` [PATCH 4/4] HAX: DO NOT MERGE Kunal Joshi
2025-01-15 10:16 ` ✗ GitLab.Pipeline: warning for add test to validate uhbr/non-uhbr over sst/mst (rev2) Patchwork
2025-01-15 10:36 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-01-15 10:40 ` ✗ i915.CI.BAT: " Patchwork
2025-01-15 17:39 ` ✗ Xe.CI.Full: " Patchwork
2025-01-27 12:31 ` Jani Nikula [this message]
2025-01-28 7:05 ` [PATCH 0/4] add test to validate uhbr/non-uhbr over sst/mst Joshi, Kunal1
2025-01-28 15:04 ` Jani Nikula
2025-02-03 8:04 ` Joshi, Kunal1
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=87tt9ka16b.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kunal1.joshi@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