public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Bilal, Mohammed" <mohammed.bilal@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"B, Jeevan" <jeevan.b@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/kms_dirtyfb: Skip output which doesn't support PSR
Date: Tue, 17 Mar 2026 07:52:14 +0000	[thread overview]
Message-ID: <cbd6ea5ebaaa79af5f5465c1071a7fdcfe2239d4.camel@intel.com> (raw)
In-Reply-To: <LV2PR11MB604595209F1B21D2B75BFEC78141A@LV2PR11MB6045.namprd11.prod.outlook.com>

On Tue, 2026-03-17 at 05:58 +0000, Bilal, Mohammed wrote:
> Hi Jeevan ,
> 
> > -----Original Message-----
> > From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of
> > Jeevan B
> > Sent: 17 March 2026 11:02
> > To: igt-dev@lists.freedesktop.org
> > Cc: Hogander, Jouni <jouni.hogander@intel.com>; B, Jeevan
> > <jeevan.b@intel.com>
> > Subject: [PATCH i-g-t] tests/intel/kms_dirtyfb: Skip output which
> > doesn't support
> > PSR
> > 
> > Pass the actual output to psr_sink_support() instead of NULL so
> > that PSR sink
> > support is checked per-output rather than generically.

I think you should go through all igt_psr calls in kms_dirtyfb.

BR,
Jouni Högander

> > 
> > Signed-off-by: Jeevan B <jeevan.b@intel.com>
> > ---
> >  tests/intel/kms_dirtyfb.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/tests/intel/kms_dirtyfb.c b/tests/intel/kms_dirtyfb.c
> > index
> > b85e09346..36eee29db 100644
> > --- a/tests/intel/kms_dirtyfb.c
> > +++ b/tests/intel/kms_dirtyfb.c
> > @@ -120,8 +120,8 @@ static bool check_support(data_t *data)
> >  			return false;
> >  		}
> >  		if (!psr_sink_support(data->drm_fd, data-
> > >debugfs_fd,
> > -				      PSR_MODE_1, NULL)) {
> > -			igt_info("Output doesn't support PSR\n");
> > +				      PSR_MODE_1, data->output)) {
> > +			igt_info("Output %s doesn't support
> > PSR\n",
> > +igt_output_name(data->output));
> >  			return false;
> >  		}
> >  		return true;
> > --
> > 2.43.0
> 
> LGTM.
> 
> Reviewed-by: Mohammed Bilal <mohammed.bilal@intel.com>
> 


  reply	other threads:[~2026-03-17  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17  5:31 [PATCH i-g-t] tests/intel/kms_dirtyfb: Skip output which doesn't support PSR Jeevan B
2026-03-17  5:58 ` Bilal, Mohammed
2026-03-17  7:52   ` Hogander, Jouni [this message]
2026-03-17 16:08 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-03-17 17:04 ` ✓ i915.CI.BAT: " Patchwork
2026-03-18 20:51 ` ✓ i915.CI.Full: " Patchwork
2026-03-19  2:47 ` ✓ Xe.CI.FULL: " Patchwork

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=cbd6ea5ebaaa79af5f5465c1071a7fdcfe2239d4.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jeevan.b@intel.com \
    --cc=mohammed.bilal@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