From: "Kahola, Mika" <mika.kahola@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_plane_scaling: Ensure minimum height and width for planar uyv formats
Date: Thu, 21 Mar 2019 09:08:40 +0000 [thread overview]
Message-ID: <3aa8fc88c8330b2f702f6595e13b28504ef1b371.camel@intel.com> (raw)
In-Reply-To: <20190320163517.GS3888@intel.com>
Thanks for the reviews!
The patch is now pushed.
I could add is_i915 check as this is probably needed for i915.
Cheers,
Mika
On Wed, 2019-03-20 at 18:35 +0200, Ville Syrjälä wrote:
> On Wed, Mar 20, 2019 at 11:22:54AM +0200, Mika Kahola wrote:
> > Let's ensure that we test with minimum width and height of 16 for
> > all planar uyv formats.
> >
> > References: https://bugs.freedesktop.org/show_bug.cgi?id=110098
> > Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> > ---
> > tests/kms_plane_scaling.c | 15 ++++++++++++++-
> > 1 file changed, 14 insertions(+), 1 deletion(-)
> >
> > diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> > index d408a203..01f5f7c9 100644
> > --- a/tests/kms_plane_scaling.c
> > +++ b/tests/kms_plane_scaling.c
> > @@ -60,6 +60,19 @@ static int get_num_scalers(data_t* d, enum pipe
> > pipe)
> > return 1;
> > }
> >
> > +static bool is_planar_yuv_format(uint32_t pixelformat)
> > +{
> > + switch (pixelformat) {
> > + case DRM_FORMAT_NV12:
> > + case DRM_FORMAT_P010:
> > + case DRM_FORMAT_P012:
> > + case DRM_FORMAT_P016:
> > + return true;
> > + default:
> > + return false;
> > + }
> > +}
>
> We should probably think about exposing the format desc stuff
> outside igt_fb.
>
> Also, this should maybe have a is_i915 check since other
> hw might not need this.
>
> Anyways
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> > +
> > static void cleanup_fbs(data_t *data)
> > {
> > int i;
> > @@ -136,7 +149,7 @@ static void check_scaling_pipe_plane_rot(data_t
> > *d, igt_plane_t *plane,
> >
> > /* create buffer in the range of min and max source side
> > limit.*/
> > width = height = 8;
> > - if (pixel_format == DRM_FORMAT_NV12)
> > + if (is_planar_yuv_format(pixel_format))
> > width = height = 16;
> > igt_create_color_fb(display->drm_fd, width, height,
> > pixel_format, tiling, 0.0, 1.0, 0.0, &d->fb[0]);
> > --
> > 2.17.1
> >
> > _______________________________________________
> > igt-dev mailing list
> > igt-dev@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/igt-dev
>
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-21 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 9:22 [igt-dev] [PATCH i-g-t] tests/kms_plane_scaling: Ensure minimum height and width for planar uyv formats Mika Kahola
2019-03-20 10:57 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-03-20 16:21 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-03-20 16:35 ` [igt-dev] [PATCH i-g-t] " Ville Syrjälä
2019-03-21 9:08 ` Kahola, Mika [this message]
2019-03-21 9:02 ` Juha-Pekka Heikkila
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=3aa8fc88c8330b2f702f6595e13b28504ef1b371.camel@intel.com \
--to=mika.kahola@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ville.syrjala@linux.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