Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Sharma, Swati2" <swati2.sharma@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_cdclk: Minor fix
Date: Wed, 7 Jul 2021 05:08:38 +0000	[thread overview]
Message-ID: <5214e95a11c1437a96d3d0f67159ff81@intel.com> (raw)
In-Reply-To: <68956fef62aa4191a9ae077da11a6820@intel.com>



> > -----Original Message-----
> > From: Sharma, Swati2 <swati2.sharma@intel.com>
> > Sent: Wednesday, July 7, 2021 2:58 AM
> > To: igt-dev@lists.freedesktop.org
> > Cc: Sharma, Swati2 <swati2.sharma@intel.com>; Shankar, Uma
> > <uma.shankar@intel.com>
> > Subject: [igt-dev][PATCH i-g-t] tests/kms_cdclk: Minor fix

Missed to call out earlier, Please rename the patch header with what is the
minor fix.  Something like: "Fix cdclock failure condition" or something similar.

> > Driver still works in a such way that we never reduce CDCLK, but
> > always only increase it. That was done in order to avoid continuous
> > CDCLK switching,
> >
> > So, in case if new CDCLK is 307200 and there is no change in CDCLK
> > beacuse of above stated driver optimization; pass the test else check lt condition.
> 
> As discussed on offline chats, enhance this test to lower modes for all connectors in
> order to lower cd clock and get a proper DVFS behavior, along with the above
> mentioned kernel change.
> 
> But for now, this change helps avoid getting false failure reports, so:
> Reviewed-by: Uma Shankar <uma.shakar@intel.com>
> 
> >
> > Cc: Uma Shankar <uma.shankar@intel.com>
> > Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> > ---
> >  tests/kms_cdclk.c | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/tests/kms_cdclk.c b/tests/kms_cdclk.c index
> > d2a9fa5f..818cbfd5 100644
> > --- a/tests/kms_cdclk.c
> > +++ b/tests/kms_cdclk.c
> > @@ -31,6 +31,7 @@ IGT_TEST_DESCRIPTION("Test cdclk features : crawling");
> >  #define HDISPLAY_4K     3840
> >  #define VDISPLAY_4K     2160
> >  #define VREFRESH	60
> > +#define MAX_CDCLK_4K    307200
> >
> >  /* Test flags */
> >  enum {
> > @@ -228,7 +229,8 @@ static void test_mode_transition(data_t *data,
> > enum pipe pipe, igt_output_t *out
> >  	igt_info("CD clock frequency %d -> %d\n", cdclk_ref, cdclk_new);
> >
> >  	/* cdclk should bump */
> > -	igt_assert_lt(cdclk_ref, cdclk_new);
> > +	if (cdclk_new != MAX_CDCLK_4K)
> > +		igt_assert_lt(cdclk_ref, cdclk_new);
> >
> >  	/* cleanup */
> >  	do_cleanup_display(display);
> > --
> > 2.25.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2021-07-07  5:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06 21:27 [igt-dev] [PATCH i-g-t] tests/kms_cdclk: Minor fix Swati Sharma
2021-07-06 21:45 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2021-07-06 22:06 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2021-07-07  5:04 ` [igt-dev] [PATCH i-g-t] " Shankar, Uma
2021-07-07  5:08   ` Shankar, Uma [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=5214e95a11c1437a96d3d0f67159ff81@intel.com \
    --to=uma.shankar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=swati2.sharma@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