From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"B, Jeevan" <jeevan.b@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/i915/kms_psr2_sf: Fix cleanup
Date: Thu, 23 Mar 2023 07:46:49 +0000 [thread overview]
Message-ID: <9d27a515b6f8616c8843022b677190fabc92085f.camel@intel.com> (raw)
In-Reply-To: <DM4PR11MB6312C198ECD11440E90784FC90879@DM4PR11MB6312.namprd11.prod.outlook.com>
On Thu, 2023-03-23 at 07:43 +0000, B, Jeevan wrote:
> Can we set display_reset before setting pipe ??
I don't know about that, but logically as prepare is setting pipe for
output I would expect cleanup to release it.
>
> > -----Original Message-----
> > From: Hogander, Jouni <jouni.hogander@intel.com>
> > Sent: Thursday, March 23, 2023 1:08 PM
> > 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/i915/kms_psr2_sf: Fix cleanup
> >
> > Cleanup is leaving pipe reserved. This is causing failures like:
> >
> > igt_kms-CRITICAL: DP-1 and eDP-1 are both trying to use pipe A
> >
> > Fix by setting pipe of output as PIPE_NONE.
> >
> > Cc: Jeevan B <jeevan.b@intel.com>
> >
> > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > ---
> > tests/i915/kms_psr2_sf.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/tests/i915/kms_psr2_sf.c b/tests/i915/kms_psr2_sf.c
> > index
> > 2d761d31..4a8608c1 100644
> > --- a/tests/i915/kms_psr2_sf.c
> > +++ b/tests/i915/kms_psr2_sf.c
> > @@ -846,10 +846,10 @@ static void cleanup(data_t *data)
> > igt_plane_set_fb(sprite, NULL);
> > }
> >
> > - if (data->coexist_feature & FEATURE_DSC) {
> > + if (data->coexist_feature &
> > FEATURE_DSC)https://patchwork.freedesktop.org/series/115532/
> > restore_force_dsc_en();
> > - igt_output_set_pipe(output, PIPE_NONE);
> > - }
> > +
> > + igt_output_set_pipe(output, PIPE_NONE);
> >
> > igt_display_commit2(&data->display, COMMIT_ATOMIC);
> >
> > --
> > 2.34.1
>
next prev parent reply other threads:[~2023-03-23 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 7:37 [igt-dev] [PATCH i-g-t] tests/i915/kms_psr2_sf: Fix cleanup Jouni Högander
2023-03-23 7:43 ` B, Jeevan
2023-03-23 7:46 ` Hogander, Jouni [this message]
2023-03-23 7:51 ` B, Jeevan
2023-03-23 8:29 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-03-23 10:17 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-03-27 7:02 ` Hogander, Jouni
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=9d27a515b6f8616c8843022b677190fabc92085f.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@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