Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
Subject: Re: [igt-dev] [i-g-t 4/5] tests/intel/kms_dirtyfb: Use blitter if rendercopy isn't present
Date: Wed, 15 Nov 2023 10:17:02 +0000	[thread overview]
Message-ID: <29d8c8952c9885f46f8ce8c8b46a6d9df1b6c0a0.camel@intel.com> (raw)
In-Reply-To: <20231115070344.1488683-5-bhanuprakash.modem@intel.com>

On Wed, 2023-11-15 at 12:33 +0530, Bhanuprakash Modem wrote:
> As Rendercopy support in IGT is not present for few latest
> platforms. So, fallback to use Blitter if Rendercopy isn't
> present.

When you have fixed patch 3. I'm fine with this patch as well:

Reviewed-by: Jouni Högander <jouni.hogander@intel.com>

> 
> Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> Cc: Jouni Högander <jouni.hogander@intel.com>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> ---
>  tests/intel/kms_dirtyfb.c | 14 +++++++++-----
>  1 file changed, 9 insertions(+), 5 deletions(-)
> 
> diff --git a/tests/intel/kms_dirtyfb.c b/tests/intel/kms_dirtyfb.c
> index c072c221d..a0f61b7a3 100644
> --- a/tests/intel/kms_dirtyfb.c
> +++ b/tests/intel/kms_dirtyfb.c
> @@ -237,8 +237,6 @@ static void run_test(data_t *data)
>         igt_render_copyfunc_t rendercopy =
> igt_get_render_copyfunc(devid);
>         int r;
>  
> -       igt_skip_on(!rendercopy);
> -
>         src = intel_buf_create_full(data->bops, data-
> >fbs[1].gem_handle,
>                                     data->fbs[1].width,
>                                     data->fbs[1].height,
> @@ -259,13 +257,19 @@ static void run_test(data_t *data)
>         spin = igt_spin_new(data->drm_fd, .ahnd = ibb-
> >allocator_handle);
>         igt_spin_set_timeout(spin, NSEC_PER_SEC);
>  
> -       rendercopy(ibb, src, 0, 0, data->fbs[2].width, data-
> >fbs[2].height, dst, 0, 0);
> +       if (rendercopy) {
> +               rendercopy(ibb, src, 0, 0, data->fbs[2].width, data-
> >fbs[2].height, dst, 0, 0);
> +       } else {
> +               intel_bb_blt_copy(ibb, src, 0, 0, src-
> >surface[0].stride,
> +                                 dst, 0, 0, dst->surface[0].stride,
> +                                 data->fbs[2].width, data-
> >fbs[2].height, dst->bpp);
> +       }
>  
> -       /* Perfom dirtyfb right after initiating rendercopy */
> +       /* Perfom dirtyfb right after initiating rendercopy/blitter
> */
>         r = drmModeDirtyFB(data->drm_fd, data->fbs[2].fb_id, NULL,
> 0);
>         igt_assert(r == 0 || r == -ENOSYS);
>  
> -       /* Ensure rendercopy is complete */
> +       /* Ensure rendercopy/blitter is complete */
>         intel_bb_sync(ibb);
>  
>         igt_pipe_crc_collect_crc(data->pipe_crc, &crc);


  reply	other threads:[~2023-11-15 10:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15  7:03 [igt-dev] [i-g-t 0/5] Fix the usage of Rendercopy in KMS tests Bhanuprakash Modem
2023-11-15  7:03 ` [igt-dev] [i-g-t 1/5] tests/intel/kms_fbt: Use blitter as a default draw method Bhanuprakash Modem
2023-11-15  7:03 ` [igt-dev] [i-g-t 2/5] tests/intel/kms_fbt: Fill fb region with requested " Bhanuprakash Modem
2023-11-15  7:03 ` [igt-dev] [i-g-t 3/5] tests/intel/kms_dirtyfb: Use blitter as a default " Bhanuprakash Modem
2023-11-15 10:15   ` Hogander, Jouni
2023-11-15 12:56     ` Modem, Bhanuprakash
2023-11-15  7:03 ` [igt-dev] [i-g-t 4/5] tests/intel/kms_dirtyfb: Use blitter if rendercopy isn't present Bhanuprakash Modem
2023-11-15 10:17   ` Hogander, Jouni [this message]
2023-11-15  7:03 ` [igt-dev] [i-g-t 5/5] tests/intel/kms_dirtyfb: Restructure dynamic subtests Bhanuprakash Modem
2023-11-15 10:19   ` Hogander, Jouni
2023-11-15 12:39     ` Modem, Bhanuprakash
2023-11-15  8:16 ` [igt-dev] ✓ Fi.CI.BAT: success for Fix the usage of Rendercopy in KMS tests Patchwork
2023-11-15  8:51 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-11-17  0:33 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=29d8c8952c9885f46f8ce8c8b46a6d9df1b6c0a0.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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