From: "Joshi, Kunal1" <kunal1.joshi@intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [i-g-t,v3,2/3] tests/intel/kms_psr2_sf: Check pipe and output validity for Selective Fetch test
Date: Fri, 6 Feb 2026 11:28:38 +0530 [thread overview]
Message-ID: <89144a93-6330-4323-8905-5a3d4abd572f@intel.com> (raw)
In-Reply-To: <20260205070425.300934-3-jouni.hogander@intel.com>
On 05-02-2026 12:34, Jouni Högander wrote:
> There are some restrictions in pipe usage for PSR2/PR Selective
> Fetch. Implement helper to checks these restrictions and use it to figure
> out if pipe/PSR/PR combo in data_t is valid. Also check if used output
> supports PSR/PR.
>
> v3:
> - use data->devid instead of intel_get_drm_devi
> - changed IS_ALDERLAKE_S to !IS_ALDERLAKE_P
> v2: rebase and commit message updated
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
Reviewed-by: Kunal Joshi <kunal1.joshi@intel.com>
next prev parent reply other threads:[~2026-02-06 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 7:04 [PATCH i-g-t v3 0/3] Run PSR2 and PR tests on panel supporting both Jouni Högander
2026-02-05 7:04 ` [PATCH i-g-t v3 1/3] tests/intel/kms_psr2_sf: Drop Early Transport flag from data_t Jouni Högander
2026-02-05 7:04 ` [PATCH i-g-t v3 2/3] tests/intel/kms_psr2_sf: Check pipe and output validity for Selective Fetch test Jouni Högander
2026-02-06 5:58 ` Joshi, Kunal1 [this message]
2026-02-06 6:38 ` [i-g-t,v3,2/3] " Hogander, Jouni
2026-02-05 7:04 ` [PATCH i-g-t v3 3/3] tests/kms_psr2_sf: Allow testing of both PSR2 and Panel Replay if supported Jouni Högander
2026-02-05 8:06 ` ✓ Xe.CI.BAT: success for Run PSR2 and PR tests on panel supporting both (rev3) Patchwork
2026-02-05 8:36 ` ✓ i915.CI.BAT: " Patchwork
2026-02-05 23:20 ` ✗ i915.CI.Full: failure " Patchwork
2026-02-06 2:48 ` ✗ 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=89144a93-6330-4323-8905-5a3d4abd572f@intel.com \
--to=kunal1.joshi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jouni.hogander@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