All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-media@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
	Michael Rodin <mrodin@de.adit-jv.com>,
	LUU HOAI <hoai.luu.ub@renesas.com>
Subject: Re: [PATCH] media: v4l: vsp1: Fix offset calculation for plane cropping
Date: Mon, 28 Feb 2022 12:35:34 +0000	[thread overview]
Message-ID: <164605173440.2091767.1596016124776932401@Monstersaurus> (raw)
In-Reply-To: <20220228120058.9755-1-laurent.pinchart+renesas@ideasonboard.com>

Quoting Laurent Pinchart (2022-02-28 12:00:58)
> From: Michael Rodin <mrodin@de.adit-jv.com>
> 
> The vertical subsampling factor is currently not considered in the
> offset calculation for plane cropping done in rpf_configure_partition.
> This causes a distortion (shift of the color plane) when formats with
> the vsub factor larger than 1 are used (e.g. NV12, see
> vsp1_video_formats in vsp1_pipe.c). This commit considers vsub factor
> for all planes except plane 0 (luminance).
> 
> Fixes: e5ad37b64de9 ("[media] v4l: vsp1: Add cropping support")
> Signed-off-by: Michael Rodin <mrodin@de.adit-jv.com>
> Signed-off-by: LUU HOAI <hoai.luu.ub@renesas.com>
> 
> Drop generalization of the offset calculation to reduce the binary size.
> 
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>

Looks fine to me, and I now see that the extra tests identify the
failure experienced and resolve it so...

Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>

> ---
>  drivers/media/platform/vsp1/vsp1_rpf.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/media/platform/vsp1/vsp1_rpf.c b/drivers/media/platform/vsp1/vsp1_rpf.c
> index 85587c1b6a37..75083cb234fe 100644
> --- a/drivers/media/platform/vsp1/vsp1_rpf.c
> +++ b/drivers/media/platform/vsp1/vsp1_rpf.c
> @@ -291,11 +291,11 @@ static void rpf_configure_partition(struct vsp1_entity *entity,
>                      + crop.left * fmtinfo->bpp[0] / 8;
>  
>         if (format->num_planes > 1) {
> +               unsigned int bpl = format->plane_fmt[1].bytesperline;
>                 unsigned int offset;
>  
> -               offset = crop.top * format->plane_fmt[1].bytesperline
> -                      + crop.left / fmtinfo->hsub
> -                      * fmtinfo->bpp[1] / 8;
> +               offset = crop.top / fmtinfo->vsub * bpl
> +                      + crop.left / fmtinfo->hsub * fmtinfo->bpp[1] / 8;
>                 mem.addr[1] += offset;
>                 mem.addr[2] += offset;
>         }
> -- 
> Regards,
> 
> Laurent Pinchart
>

  reply	other threads:[~2022-02-28 12:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 12:00 [PATCH] media: v4l: vsp1: Fix offset calculation for plane cropping Laurent Pinchart
2022-02-28 12:35 ` Kieran Bingham [this message]
2022-03-02 11:00 ` Michael Rodin
2022-04-14 14:20   ` Laurent Pinchart
2022-04-19 10:22     ` Michael Rodin
2022-05-06  9:58       ` Michael Rodin
2022-05-07 21:16         ` Laurent Pinchart

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=164605173440.2091767.1596016124776932401@Monstersaurus \
    --to=kieran.bingham@ideasonboard.com \
    --cc=hoai.luu.ub@renesas.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mrodin@de.adit-jv.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.