From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>,
Mohammed Thasleem <mohammed.thasleem@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2 2/2] tests/i915/kms_cdclk: Fixed mode selection for MST modeset
Date: Fri, 9 Jun 2023 12:51:03 +0530 [thread overview]
Message-ID: <7444d1c8-2c3f-bb0d-c26f-d2ac4726d9a2@intel.com> (raw)
In-Reply-To: <0caf9817-8cff-0eb4-fa78-7187d5433431@intel.com>
On 08-Jun-23 4:47 PM, Modem, Bhanuprakash wrote:
> Hi Thasleem,
>
> On Wed-07-06-2023 05:23 pm, Mohammed Thasleem wrote:
>> When two monitors connected through MST. This will find the
>> connector mode combo that fits into the bandwidth when more
>> than one monitor is connected.
>>
>> Example:
>> When two monitors connected through MST, the second monitor
>> also tries to use the same mode. So two such modes may not
>> fit into the link bandwidth. So, iterate through connected
>> outputs & modes and find a combination of modes those fit
>> into the link BW.
>>
>> v2: -Removed if loop checks.
>> -Added igt override to avoid dp mst bw failure.
>> v3: Rebased on tip.
>>tip??
>>
>> Signed-off-by: Mohammed Thasleem <mohammed.thasleem@intel.com>
>> ---
>> tests/i915/kms_cdclk.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/tests/i915/kms_cdclk.c b/tests/i915/kms_cdclk.c
>> index 0f9b8dc5..bf93d940 100644
>> --- a/tests/i915/kms_cdclk.c
>> +++ b/tests/i915/kms_cdclk.c
>> @@ -257,6 +257,7 @@ static void
>> test_mode_transition_on_all_outputs(data_t *data)
>> int valid_outputs = 0;
>> int cdclk_ref, cdclk_new;
>> uint16_t width = 0, height = 0;
>> + bool found;
>> struct igt_fb fb;
>> igt_pipe_t *pipe;
>> igt_plane_t *plane;
>> @@ -332,6 +333,10 @@ static void
>> test_mode_transition_on_all_outputs(data_t *data)
>> j++;
>> }
>> + /* In case of DP-MST find suitable mode(s) to fit into the link
>> BW. */
>> + found = igt_override_all_active_output_modes_to_fit_bw(display);
>> + igt_require_f(found, "No valid mode combo found for MST
>> modeset.\n");
>
> This is not correct.
>
> If this logic overrides any display mode to less than 4K, you can't see
> the clock bumpup which leads to the test failure.
>
> @Swati, any thoughts?
>> Right. Yes, this is tested. When we transition from lower mode to 4k
we do see cdclk bump. For rest of the cases not sure.
>
> - Bhanu
>
>> +
>> igt_display_commit2(display, COMMIT_ATOMIC);
>> cdclk_new = get_current_cdclk_freq(debugfs_fd);
>> igt_info("CD clock frequency %d -> %d\n", cdclk_ref, cdclk_new);
next prev parent reply other threads:[~2023-06-09 7:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 11:53 [igt-dev] [PATCH i-g-t v2 0/2] Fixed mode selection for MST modeset Mohammed Thasleem
2023-06-07 11:53 ` [igt-dev] [PATCH i-g-t v2 1/2] tests/kms_display_modes: Fixed mode selection for extended mode tests Mohammed Thasleem
2023-06-08 11:26 ` Modem, Bhanuprakash
2023-06-25 18:34 ` [igt-dev] [PATCH v3 " Mohammed Thasleem
2023-06-26 11:01 ` Modem, Bhanuprakash
2023-06-27 18:55 ` [igt-dev] [PATCH v4 " Mohammed Thasleem
2023-06-28 7:36 ` Modem, Bhanuprakash
2023-07-03 5:38 ` [igt-dev] [PATCH v5 " Thasleem, Mohammed
2023-06-07 11:53 ` [igt-dev] [PATCH i-g-t v2 2/2] tests/i915/kms_cdclk: Fixed mode selection for MST modeset Mohammed Thasleem
2023-06-08 11:17 ` Modem, Bhanuprakash
2023-06-09 7:21 ` Sharma, Swati2 [this message]
2023-06-27 20:34 ` [igt-dev] [PATCH v3 " Mohammed Thasleem
2023-07-03 6:26 ` [igt-dev] [PATCH v4 " Thasleem, Mohammed
2023-06-07 13:22 ` [igt-dev] ✗ GitLab.Pipeline: warning for Fixed mode selection for MST modeset (rev4) Patchwork
2023-06-07 13:48 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-08 2:06 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-06-08 6:17 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev5) Patchwork
2023-06-08 11:43 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Fixed mode selection for MST modeset (rev6) Patchwork
2023-06-09 4:22 ` [igt-dev] ✗ Fi.CI.IGT: failure for Fixed mode selection for MST modeset (rev5) Patchwork
2023-06-25 19:26 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev7) Patchwork
2023-06-25 20:46 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-06-27 20:06 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev8) Patchwork
2023-06-27 21:47 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev9) Patchwork
2023-06-28 12:50 ` [igt-dev] ✗ Fi.CI.IGT: failure for Fixed mode selection for MST modeset (rev8) Patchwork
2023-06-28 15:48 ` [igt-dev] ✗ Fi.CI.IGT: failure for Fixed mode selection for MST modeset (rev9) Patchwork
2023-07-03 6:44 ` [igt-dev] ✗ Fi.CI.BAT: failure for Fixed mode selection for MST modeset (rev10) Patchwork
2023-07-03 7:08 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev11) Patchwork
2023-07-03 8:19 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-07-05 13:07 ` [igt-dev] ✗ Fi.CI.BAT: failure for Fixed mode selection for MST modeset (rev12) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-06-07 11:25 [igt-dev] [PATCH i-g-t v2 0/2] Fixed mode selection for MST modeset Mohammed Thasleem
2023-06-07 11:25 ` [igt-dev] [PATCH i-g-t v2 2/2] tests/i915/kms_cdclk: " Mohammed Thasleem
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=7444d1c8-2c3f-bb0d-c26f-d2ac4726d9a2@intel.com \
--to=swati2.sharma@intel.com \
--cc=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mohammed.thasleem@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