From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Karthik B S <karthik.b.s@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2] tests/kms_invalid_mode: Skip clock-too-high subtest on DSC panel
Date: Tue, 17 May 2022 10:48:26 +0300 [thread overview]
Message-ID: <YoNTStoMBn3nRWO0@intel.com> (raw)
In-Reply-To: <20220516035255.28288-1-karthik.b.s@intel.com>
On Mon, May 16, 2022 at 09:22:55AM +0530, Karthik B S wrote:
> Max clock limit calculation isn't valid with DSC.
What does it have to do with DSC?
> Skip the test on DSC panels.
>
> Fixes: https://gitlab.freedesktop.org/drm/intel/-/issues/4402
>
> Signed-off-by: Karthik B S <karthik.b.s@intel.com>
> ---
> tests/kms_invalid_mode.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/kms_invalid_mode.c b/tests/kms_invalid_mode.c
> index bb92a94e..cf011a17 100644
> --- a/tests/kms_invalid_mode.c
> +++ b/tests/kms_invalid_mode.c
> @@ -73,6 +73,8 @@ adjust_mode_clock_too_high(data_t *data, drmModeModeInfoPtr mode)
> int max_dotclock = data->max_dotclock;
>
> igt_require(max_dotclock != 0);
> + igt_require(!igt_is_dsc_supported(data->drm_fd,
> + data->output->config.connector));
>
> /*
> * FIXME When we have a fixed mode, the kernel will ignore
> --
> 2.22.0
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-05-17 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 3:52 [igt-dev] [PATCH i-g-t v2] tests/kms_invalid_mode: Skip clock-too-high subtest on DSC panel Karthik B S
2022-05-16 4:58 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_invalid_mode: Skip clock-too-high subtest on DSC panel (rev2) Patchwork
2022-05-16 5:58 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-17 7:48 ` Ville Syrjälä [this message]
2022-05-17 18:29 ` [igt-dev] [PATCH i-g-t v2] tests/kms_invalid_mode: Skip clock-too-high subtest on DSC panel Navare, Manasi
2022-05-18 12:38 ` Ville Syrjälä
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=YoNTStoMBn3nRWO0@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.