From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: "Sebastian Dröge" <sebastian.droege@collabora.co.uk>
Cc: sylvester.nawrocki@gmail.com, LMML <linux-media@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: FIMC/CAMIF V4L2 driver
Date: Fri, 11 Jan 2013 12:26:27 +0100 [thread overview]
Message-ID: <50EFF6E3.4090302@samsung.com> (raw)
In-Reply-To: <1357902525.6914.139.camel@thor.lan>
Hi,
On 01/11/2013 12:08 PM, Sebastian Dröge wrote:
> I can't test the patch right now but it should do almost the right
> thing. IMHO for the chroma planes the bytesperline should be (width
> +1)/2, otherwise you'll miss one chroma value per line for odd widths.
Odd widths are not allowed, the driver will adjust width to be multiple
of 16 pixels. However, you can adjust the usable area more precisely with
VIDIOC_S_CROP or VIDIOC_S_SELECTION ioctl. I still need to do some work to
define properly the selection ioctl on mem-to-mem devices in the V4L2
documentation.
> However I also noticed another bug. Currently S_FMT happily allows
> V4L2_PIX_FMT_BGR32, V4L2_PIX_FMT_BGR24, V4L2_PIX_FMT_RGB24 and probably
> others. But the output will be distorted and useless.
> (V4L2_PIX_FMT_RGB32 works perfectly fine)
This shouldn't really happen. Are you checking pixelformat after VIDIOC_S_FMT
call ? Isn't it adjusted to some valid and supported by the driver format ?
--
Regards,
Sylwester
next prev parent reply other threads:[~2013-01-11 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1356685333.4296.92.camel@thor.lan>
2013-01-11 10:39 ` FIMC/CAMIF V4L2 driver Sylwester Nawrocki
2013-01-11 11:08 ` Sebastian Dröge
2013-01-11 11:26 ` Sylwester Nawrocki [this message]
2013-01-11 12:37 ` Sebastian Dröge
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=50EFF6E3.4090302@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sebastian.droege@collabora.co.uk \
--cc=sylvester.nawrocki@gmail.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.