From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Pekka Paalanen <pekka.paalanen@collabora.com>
Cc: igt-dev@lists.freedesktop.org, "Simon Ser" <contact@emersion.fr>,
"Jonas Ådahl" <jadahl@redhat.com>,
"Daniel Stone" <daniel@fooishbar.org>,
"Sameer Lattannavar" <sameer.lattannavar@intel.com>,
"Sebastian Wick" <sebastian.wick@redhat.com>,
"Harry Wentland" <harry.wentland@amd.com>
Subject: Re: [PATCH i-g-t 4/5] tests/kms_cursor_crc: Test the SIZE_HINTS property
Date: Thu, 4 Apr 2024 16:05:32 +0300 [thread overview]
Message-ID: <Zg6lnKuoVrR5OjK8@intel.com> (raw)
In-Reply-To: <20240404155250.7fb245d2.pekka.paalanen@collabora.com>
On Thu, Apr 04, 2024 at 03:52:50PM +0300, Pekka Paalanen wrote:
> On Thu, 4 Apr 2024 13:56:02 +0300
> Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
>
> > On Thu, Apr 04, 2024 at 11:51:05AM +0300, Pekka Paalanen wrote:
> > > On Fri, 15 Mar 2024 21:15:04 +0200
> > > Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> > >
> > > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > >
> > > > Make sure the driver accepts all the sizes declared in the
> > > > plane's SIZE_HINTS property.
> > > >
> > > > TODO: Actually test that each reported size works fully?
> > >
> > > What does this mean? What does cursor_size_supported() do?
> >
> > It does a TEST_ONLY commit using data->fb and the specified size.
> > So just confirms that the kernel accepts it, not that it actually
> > looks correct on screen.
>
> Good, that's better than my first impression.
>
> > > I don't know that, so it looks like you just create an FB and destroy
> > > it, never putting it on the plane where the SIZE_HINTS were found.
> > >
> > > > Would need a bunch of restructuring of the test,
> > > > and for the moment i915 is the only driver that
> > > > supports SIZE_HINTS and it's already >100% covered
> > > > by the existing tests. So I'll leave this for the
> > > > next guy whose driver has different needs...
> > >
> > > How would they know to fix this test? They just see the test pass and
> > > are happy, right?
> >
> > I would expect them to actually care about testing their driver
> > properly. But perhaps my expectations are a bit high.
>
> Yeah, a screenshot or CRC test would be best.
Yep. We have CRC tests, but the impelementation would need to be
completely flipped on its head to iterate the sizes as the inner
loop rather than as the outer loop. Not impossible, just a bunch
of work (and wouldn't extend the coverage for i915 at all).
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-04-04 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 19:15 [PATCH i-g-t 0/5] tests/kms_cursor_crc: Test SIZE_HINTS Ville Syrjala
2024-03-15 19:15 ` [PATCH i-g-t 1/5] wip: drm-uapi: add drm_plane_size_hints Ville Syrjala
2024-03-15 19:15 ` [PATCH i-g-t 2/5] lib/igt_kms: Add IGT_PLANE_SIZE_HINTS Ville Syrjala
2024-03-15 19:15 ` [PATCH i-g-t 3/5] tests/kms_cursor_crc: Make require_cursor_size() a bit more sensible Ville Syrjala
2024-03-15 19:15 ` [PATCH i-g-t 4/5] tests/kms_cursor_crc: Test the SIZE_HINTS property Ville Syrjala
2024-04-04 8:51 ` Pekka Paalanen
2024-04-04 10:56 ` Ville Syrjälä
2024-04-04 12:52 ` Pekka Paalanen
2024-04-04 13:05 ` Ville Syrjälä [this message]
2024-03-15 19:15 ` [PATCH i-g-t 5/5] CI: tests/intel-ci: Run kms_cursor_crc@cursor-size-hints Ville Syrjala
2024-03-15 20:09 ` ✓ CI.xeBAT: success for tests/kms_cursor_crc: Test SIZE_HINTS Patchwork
2024-03-15 20:11 ` ✓ Fi.CI.BAT: " Patchwork
2024-03-16 21:18 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-18 10:45 ` [PATCH i-g-t 0/5] " Sebastian Wick
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=Zg6lnKuoVrR5OjK8@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=contact@emersion.fr \
--cc=daniel@fooishbar.org \
--cc=harry.wentland@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jadahl@redhat.com \
--cc=pekka.paalanen@collabora.com \
--cc=sameer.lattannavar@intel.com \
--cc=sebastian.wick@redhat.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