From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "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_psr2_sf: Fix primary_format setting
Date: Mon, 18 Dec 2023 12:12:39 +0000 [thread overview]
Message-ID: <3078182a95bbba4e94abcf6f621e944109e059c4.camel@intel.com> (raw)
In-Reply-To: <20231214154219.2638408-1-jeevan.b@intel.com>
Hi jeevan,
This might not be enough.
For example, if you are executing all the tests, after the first iteration y = 0, the
data.primary_format is set to DRM_FORMAT_NV12. Then in y = 1 (FBC cases) will be executed with
format as DRM_FORMAT_NV12 which will fail.
After introducing the FBC on/off loop, I think there could be other issues as well, because "data"
members are directly modified as required by the tests in that loop.
Also for pre-lnl platforms, do we need to even list and execute "fbc-" cases as it is not suported
and will be skipped?
BR
Vinod
On Thu, 2023-12-14 at 21:12 +0530, Jeevan B wrote:
> The format is being changed globally to DRM_FORMAT_NV12. additionally,
> FBC doesn't support the NV12 format, so this issue is being addressed.
>
> Signed-off-by: Jeevan B <jeevan.b@intel.com>
> ---
> tests/intel/kms_psr2_sf.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/tests/intel/kms_psr2_sf.c b/tests/intel/kms_psr2_sf.c
> index 76435f501..272260cdf 100644
> --- a/tests/intel/kms_psr2_sf.c
> +++ b/tests/intel/kms_psr2_sf.c
> @@ -1387,7 +1387,6 @@ igt_main
> * plane and continuous updates.
> */
> data.op = PLANE_UPDATE_CONTINUOUS;
> - data.primary_format = DRM_FORMAT_NV12;
> igt_describe("Test that selective fetch works on overlay plane");
> igt_subtest_with_dynamic_f("%soverlay-%s-sf", append_fbc_subtest[y],
> op_str(data.op)) {
> @@ -1404,6 +1403,11 @@ igt_main
> data.pipe = pipes[i];
> data.output = outputs[i];
> data.damage_area_count = 1;
> + if (data.fbc_flag == true &&
> + data.op_fbc_mode == FBC_ENABLED)
> + data.primary_format = DRM_FORMAT_XRGB8888;
> + else
> + data.primary_format = DRM_FORMAT_NV12;
> data.test_plane_id = DRM_PLANE_TYPE_OVERLAY;
> data.coexist_feature = j;
> prepare(&data);
next prev parent reply other threads:[~2023-12-18 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 15:42 [PATCH i-g-t] tests/intel/kms_psr2_sf: Fix primary_format setting Jeevan B
2023-12-14 16:46 ` ✓ CI.xeBAT: success for " Patchwork
2023-12-14 16:54 ` ✓ Fi.CI.BAT: " Patchwork
2023-12-14 17:53 ` ✗ Fi.CI.IGT: failure " Patchwork
2023-12-18 12:12 ` Govindapillai, Vinod [this message]
2023-12-19 6:43 ` [PATCH i-g-t] " B, Jeevan
2023-12-19 7:12 ` Govindapillai, Vinod
-- strict thread matches above, loose matches on Subject: below --
2023-12-20 18:31 Jeevan B
2023-12-21 9:16 ` Govindapillai, Vinod
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=3078182a95bbba4e94abcf6f621e944109e059c4.camel@intel.com \
--to=vinod.govindapillai@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