From: Matt Roper <matthew.d.roper@intel.com>
To: "Sharma, Swati2" <swati2.sharma@intel.com>
Cc: Vinod Govindapillai <vinod.govindapillai@intel.com>,
<igt-dev@lists.freedesktop.org>, <juha-pekka.heikkila@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/kms:cdclk: skip cdclk tests for bmg
Date: Fri, 30 Aug 2024 09:19:59 -0700 [thread overview]
Message-ID: <20240830161959.GI5091@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <089b88c8-0d44-47c1-9898-df567a475389@intel.com>
On Fri, Aug 30, 2024 at 02:27:05PM +0530, Sharma, Swati2 wrote:
> Hi Vinod,
>
> Please fix the subject.
> ++Matt for his feedback
Yeah, due to Wa_15015413771 there's only a single possible cdclk value
on Xe2_HPD, so we won't be able to trigger any cdclk changes in igt
tests. It might be worth actually putting that workaround number in the
comment to make it clear why BMG is special, but:
Acked-by: Matt Roper <matthew.d.roper@intel.com>
Matt
>
> On 13-Aug-24 4:37 PM, Vinod Govindapillai wrote:
> > As there is only one cdclk option in BMG, these cdclk tests
> > which look for change in cdclk frequency when changing
> > between high and low resolution mode will fail. So skip
> > these tests for bmg
> >
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > ---
> > tests/intel/kms_cdclk.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/tests/intel/kms_cdclk.c b/tests/intel/kms_cdclk.c
> > index 6fe6e6c3f..24a0c4547 100644
> > --- a/tests/intel/kms_cdclk.c
> > +++ b/tests/intel/kms_cdclk.c
> > @@ -402,6 +402,9 @@ igt_main
> > "Hardware doesn't support crawling/squashing.\n");
> > igt_display_require(&data.display, data.drm_fd);
> > igt_display_require_output(&data.display);
> > +
> > + /* Only one cdclk option in bmg. Skip all these tests for BMG? */
> > + igt_require(!IS_BATTLEMAGE(data.devid));
> > }
> > igt_describe("Plane scaling test to validate cdclk frequency change.");
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
prev parent reply other threads:[~2024-08-30 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 11:07 [PATCH i-g-t] tests/intel/kms:cdclk: skip cdclk tests for bmg Vinod Govindapillai
2024-08-13 11:49 ` ✓ CI.xeBAT: success for " Patchwork
2024-08-13 12:00 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-13 14:27 ` ✗ CI.xeFULL: failure " Patchwork
2024-08-13 18:52 ` ✓ Fi.CI.IGT: success " Patchwork
2024-08-30 8:57 ` [PATCH i-g-t] " Sharma, Swati2
2024-08-30 16:19 ` Matt Roper [this message]
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=20240830161959.GI5091@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juha-pekka.heikkila@intel.com \
--cc=swati2.sharma@intel.com \
--cc=vinod.govindapillai@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