All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Vidya Srinivas <vidya.srinivas@intel.com>, igt-dev@lists.freedesktop.org
Cc: sunil.kamath@intel.com, ville.syrjala@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t] [i-g-t] tests/kms_plane_scaling: Change minimum fb height for YUV 420 planar
Date: Thu, 15 Mar 2018 12:50:32 +0200	[thread overview]
Message-ID: <87woydliiv.fsf@intel.com> (raw)
In-Reply-To: <1521092542-1288-1-git-send-email-vidya.srinivas@intel.com>

On Thu, 15 Mar 2018, Vidya Srinivas <vidya.srinivas@intel.com> wrote:
> When the plane scaling is used with YUV 420 planar formats,
> the height should be a minimum of 16 scanlines as per BSpec.
> Minimum of 8 scanlines is for non-YUV 420 planar formats.
> Patch changes the minimum fb height being used in the test
> in case of YUV 420 planar (currently done for NV12, as
> that is the only planar format supported)
>
> v2: Addressed review comments from Maarten

This doesn't really say anything meaningful. In the future, please state
the actual changes.

> Signed-off-by: Uma Shankar <uma.shankar@intel.com>
> Signed-off-by: Vidya Srinivas <vidya.srinivas@intel.com>
> ---
>  tests/kms_plane_scaling.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> index 4408e5c..36fcfc0 100644
> --- a/tests/kms_plane_scaling.c
> +++ b/tests/kms_plane_scaling.c
> @@ -131,6 +131,8 @@ 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 = 9;
> +	if (pixel_format == DRM_FORMAT_NV12)
> +		width = height = 17;

IMO it's easier to read when you have an if-else instead of overwriting
the previous values in some cases.

BR,
Jani.

>  	igt_create_color_fb(display->drm_fd, width, height,
>  		       pixel_format, tiling, 0.0, 1.0, 0.0, &d->fb[0]);
>  	igt_plane_set_fb(plane, &d->fb[0]);

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2018-03-15 10:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15  5:42 [igt-dev] [PATCH i-g-t] [i-g-t] tests/kms_plane_scaling: Change minimum fb height for YUV 420 planar Vidya Srinivas
2018-03-15  6:05 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_scaling: Change minimum fb height for YUV 420 planar (rev2) Patchwork
2018-03-15  6:52 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-03-15 10:50 ` Jani Nikula [this message]
2018-03-16  2:38   ` [igt-dev] [PATCH i-g-t] [i-g-t] tests/kms_plane_scaling: Change minimum fb height for YUV 420 planar Srinivas, Vidya
2018-03-16  7:49     ` Jani Nikula
2018-03-16  8:08       ` Srinivas, Vidya
2018-03-15 17:03 ` Maarten Lankhorst
2018-03-16 13:23   ` Srinivas, Vidya
  -- strict thread matches above, loose matches on Subject: below --
2018-03-06  9:21 Vidya Srinivas
2018-03-06  9:52 ` Maarten Lankhorst
2018-03-06 10:15   ` Srinivas, Vidya
2018-03-06 15:39     ` Maarten Lankhorst
2018-03-06  9:53 ` Maarten Lankhorst
2018-03-06 10:14   ` Srinivas, Vidya

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=87woydliiv.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sunil.kamath@intel.com \
    --cc=vidya.srinivas@intel.com \
    --cc=ville.syrjala@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.