All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Swati Sharma <swati2.sharma@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [v2 0/6] Addition of new plane scaling test cases
Date: Mon, 24 Jan 2022 13:13:45 +0200	[thread overview]
Message-ID: <Ye6J6ZhEZPX25BS7@intel.com> (raw)
In-Reply-To: <20220121134833.28740-1-swati2.sharma@intel.com>

On Fri, Jan 21, 2022 at 07:18:27PM +0530, Swati Sharma wrote:
> In this series, combination of downscaling and upscaling testcases
> are added.
> 
>     v2:-Minor fixes, to prevent CI crashes
> 
> Swati Sharma (6):
>   tests/kms_plane_scaling: Removal of plane-scaling subtest
>   tests/kms_plane_scaling: Add output name in dynamic subtests
>   tests/kms_plane_scaling: Upscaling on 2 planes
>   tests/kms_plane_scaling: Downscaling on 2 planes
>   tests/kms_plane_scaling: Upscaling and downscaling scenario
>   tests/kms_plane_scaling: Add negative test to check num of scalers

Seems quite a lot of i915isms still here. Also not sure these tests
are prticualrly useful without crcs.

If this stuff is actually considered useful I propose we generalize
it into someting more like:
- subtest for testing each plane individually (can probable speed it
  up a bit for i915 by checking 1 plane per "class" like we do in
  a bunch of the other tests).
- subtest for each N plane scaling combo, probably favoring the
  "overlay" planes and adding the primary plane only last, as it
  seems more likely that those support scaling instead of the
  primary plane

Though what we really want is crc based tests that actually make
sure we get the correct stuf on screen. On platforms where we have
the nearest neighbour scaling we should be able to do this properly.
For other platforms we could use solid color fbs and still at least
make sure we didn't get any underruns.

-- 
Ville Syrjälä
Intel

      parent reply	other threads:[~2022-01-24 11:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 13:48 [igt-dev] [v2 0/6] Addition of new plane scaling test cases Swati Sharma
2022-01-21 13:48 ` [igt-dev] [v2 1/6] tests/kms_plane_scaling: Removal of plane-scaling subtest Swati Sharma
2022-01-21 13:48 ` [igt-dev] [v2 2/6] tests/kms_plane_scaling: Add output name in dynamic subtests Swati Sharma
2022-01-21 13:48 ` [igt-dev] [v2 3/6] tests/kms_plane_scaling: Upscaling on 2 planes Swati Sharma
2022-01-21 13:48 ` [igt-dev] [v2 4/6] tests/kms_plane_scaling: Downscaling " Swati Sharma
2022-01-21 13:48 ` [igt-dev] [v2 5/6] tests/kms_plane_scaling: Upscaling and downscaling scenario Swati Sharma
2022-01-21 13:48 ` [igt-dev] [v2 6/6] tests/kms_plane_scaling: Add negative test to check num of scalers Swati Sharma
2022-01-21 14:19 ` [igt-dev] ✓ Fi.CI.BAT: success for Addition of new plane scaling test cases (rev2) Patchwork
2022-01-21 17:31 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-01-24 11:13 ` Ville Syrjälä [this message]

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=Ye6J6ZhEZPX25BS7@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=swati2.sharma@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.