public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media <linux-media@vger.kernel.org>,
	"Frank Schäfer" <fschaefer.oss@googlemail.com>,
	"Devin Heitmueller" <dheitmueller@kernellabs.com>
Subject: Re: [RFCv2 PATCH] em28xx: fix bytesperline calculation in G/TRY_FMT
Date: Wed, 30 Jan 2013 07:40:30 -0200	[thread overview]
Message-ID: <20130130074030.455a1185@redhat.com> (raw)
In-Reply-To: <201301300901.22486.hverkuil@xs4all.nl>

Em Wed, 30 Jan 2013 09:01:22 +0100
Hans Verkuil <hverkuil@xs4all.nl> escreveu:

> This was part of my original em28xx patch series. That particular patch
> combined two things: this fix and the change where TRY_FMT would no
> longer return -EINVAL for unsupported pixelformats. The latter change was
> rejected (correctly), but we all forgot about the second part of the patch
> which fixed a real bug. I'm reposting just that fix.
> 
> Changes since v1:
> 
> - v1 still miscalculated the bytesperline and imagesize values (they were
>   too large).
> - G_FMT had the same calculation bug.
> 
> Tested with my em28xx.
> 
> Regards,
> 
>         Hans
> 
> The bytesperline calculation was incorrect: it used the old width instead of
> the provided width in the case of TRY_FMT, and it miscalculated the bytesperline
> value for the depth == 12 (planar YUV 4:1:1) case. For planar formats the
> bytesperline value should be the bytesperline of the widest plane, which is
> the Y plane which has 8 bits per pixel, not 12.
> 
> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> ---
>  drivers/media/usb/em28xx/em28xx-video.c |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/media/usb/em28xx/em28xx-video.c b/drivers/media/usb/em28xx/em28xx-video.c
> index 2eabf2a..6ced426 100644
> --- a/drivers/media/usb/em28xx/em28xx-video.c
> +++ b/drivers/media/usb/em28xx/em28xx-video.c
> @@ -837,8 +837,8 @@ static int vidioc_g_fmt_vid_cap(struct file *file, void *priv,
>  	f->fmt.pix.width = dev->width;
>  	f->fmt.pix.height = dev->height;
>  	f->fmt.pix.pixelformat = dev->format->fourcc;
> -	f->fmt.pix.bytesperline = (dev->width * dev->format->depth + 7) >> 3;
> -	f->fmt.pix.sizeimage = f->fmt.pix.bytesperline  * dev->height;
> +	f->fmt.pix.bytesperline = dev->width * (dev->format->depth >> 3);

Why did you remove the round up here?

> +	f->fmt.pix.sizeimage = (dev->width * dev->height * dev->format->depth + 7) >> 3;
>  	f->fmt.pix.colorspace = V4L2_COLORSPACE_SMPTE170M;
>  
>  	/* FIXME: TOP? NONE? BOTTOM? ALTENATE? */
> @@ -906,8 +906,8 @@ static int vidioc_try_fmt_vid_cap(struct file *file, void *priv,
>  	f->fmt.pix.width = width;
>  	f->fmt.pix.height = height;
>  	f->fmt.pix.pixelformat = fmt->fourcc;
> -	f->fmt.pix.bytesperline = (dev->width * fmt->depth + 7) >> 3;
> -	f->fmt.pix.sizeimage = f->fmt.pix.bytesperline * height;
> +	f->fmt.pix.bytesperline = width * (fmt->depth >> 3);

Why did you remove the round up here?

> +	f->fmt.pix.sizeimage = (width * height * fmt->depth + 7) >> 3;
>  	f->fmt.pix.colorspace = V4L2_COLORSPACE_SMPTE170M;
>  	if (dev->progressive)
>  		f->fmt.pix.field = V4L2_FIELD_NONE;


Regards,
Mauro

  reply	other threads:[~2013-01-30  9:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30  8:01 [RFCv2 PATCH] em28xx: fix bytesperline calculation in G/TRY_FMT Hans Verkuil
2013-01-30  9:40 ` Mauro Carvalho Chehab [this message]
2013-01-30  9:49   ` Hans Verkuil
2013-01-30 16:32     ` Frank Schäfer
2013-01-30 16:59       ` Hans Verkuil
2013-01-30 19:07     ` Mauro Carvalho Chehab
2013-01-31  7:16       ` Hans Verkuil
2013-01-31 10:08         ` Mauro Carvalho Chehab
2013-01-31 11:02           ` Hans Verkuil
2013-01-31 17:57           ` Frank Schäfer

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=20130130074030.455a1185@redhat.com \
    --to=mchehab@redhat.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=fschaefer.oss@googlemail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    /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