All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Eric Anholt <eric@anholt.net>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] drm/vc4: ->x_scaling[1] should never be set to VC4_SCALING_NONE
Date: Fri, 9 Nov 2018 15:31:38 +0100	[thread overview]
Message-ID: <20181109153138.65566573@bbrezillon> (raw)
In-Reply-To: <20181109102633.32603-1-boris.brezillon@bootlin.com>

On Fri,  9 Nov 2018 11:26:32 +0100
Boris Brezillon <boris.brezillon@bootlin.com> wrote:

> For the YUV conversion to work properly, ->x_scaling[1] should never
> be set to VC4_SCALING_NONE, but vc4_get_scaling_mode() might return
> VC4_SCALING_NONE if the horizontal scaling ratio exactly matches the
> horizontal subsampling factor. Add a test to turn VC4_SCALING_NONE
> into VC4_SCALING_PPF when that happens.
> 
> The old ->x_scaling[0] adjustment is dropped as I couldn't find any
> mention to this constraint in the spec and it's proven to be
> unnecessary (I tested various multi-planar YUV formats with scaling
> disabled, and all of them worked fine without this adjustment).
> 
> Fixes: fc04023fafec ("drm/vc4: Add support for YUV planes.")
> Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> Reviewed-by: Eric Anholt <eric@anholt.net>

Series queued to drm-misc-next.

> ---
> Changes in v2:
> - Remove the the ->x_scaling[0] = VC4_SCALING_PPF
>   assignment when ->is_unity is true and update the comment
> - Add Eric's R-b
> ---
>  drivers/gpu/drm/vc4/vc4_plane.c | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc4/vc4_plane.c
> index 98fae4daa08c..6caa678edcff 100644
> --- a/drivers/gpu/drm/vc4/vc4_plane.c
> +++ b/drivers/gpu/drm/vc4/vc4_plane.c
> @@ -341,12 +341,14 @@ static int vc4_plane_setup_clipping_and_scaling(struct drm_plane_state *state)
>  			vc4_get_scaling_mode(vc4_state->src_h[1],
>  					     vc4_state->crtc_h);
>  
> -		/* YUV conversion requires that horizontal scaling be enabled,
> -		 * even on a plane that's otherwise 1:1. Looks like only PPF
> -		 * works in that case, so let's pick that one.
> +		/* YUV conversion requires that horizontal scaling be enabled
> +		 * on the UV plane even if vc4_get_scaling_mode() returned
> +		 * VC4_SCALING_NONE (which can happen when the down-scaling
> +		 * ratio is 0.5). Let's force it to VC4_SCALING_PPF in this
> +		 * case.
>  		 */
> -		if (vc4_state->is_unity)
> -			vc4_state->x_scaling[0] = VC4_SCALING_PPF;
> +		if (vc4_state->x_scaling[1] == VC4_SCALING_NONE)
> +			vc4_state->x_scaling[1] = VC4_SCALING_PPF;
>  	} else {
>  		vc4_state->is_yuv = false;
>  		vc4_state->x_scaling[1] = VC4_SCALING_NONE;

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2018-11-09 14:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 10:26 [PATCH v2 1/2] drm/vc4: ->x_scaling[1] should never be set to VC4_SCALING_NONE Boris Brezillon
2018-11-09 10:26 ` [PATCH v2 2/2] drm/vc4: Prefer PPF over TPZ when dst >= 2/3 src Boris Brezillon
2018-11-09 14:31 ` Boris Brezillon [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=20181109153138.65566573@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    /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.