From: Hans Verkuil <hverkuil@xs4all.nl>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] pxa_camera transition to v4l2 standalone device
Date: Mon, 21 Mar 2016 23:49:52 +0100 [thread overview]
Message-ID: <56F07A90.8060305@xs4all.nl> (raw)
In-Reply-To: <87h9fzmozy.fsf@belgarion.home>
On 03/21/2016 11:42 PM, Robert Jarzmik wrote:
> Hans Verkuil <hverkuil@xs4all.nl> writes:
>
>>> Input ioctls:
>>> test VIDIOC_G/S_TUNER/ENUM_FREQ_BANDS: OK (Not Supported)
>>> test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
>>> test VIDIOC_S_HW_FREQ_SEEK: OK (Not Supported)
>>> test VIDIOC_ENUMAUDIO: OK (Not Supported)
>>> fail: v4l2-test-input-output.cpp(418): G_INPUT not supported for a capture device
>>
>> ENUM/G/S_INPUT is missing and is required for capture devices.
> Okay, that one will be easy I think :) It's a mono-sensor mono-videostream IP.
> I will add that when for RFC v2.
>
>>> Format ioctls:
>>> test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: OK
>>> test VIDIOC_G/S_PARM: OK (Not Supported)
>>> test VIDIOC_G_FBUF: OK (Not Supported)
>>> fail: v4l2-test-formats.cpp(329): pixelformat != V4L2_PIX_FMT_JPEG && colorspace == V4L2_COLORSPACE_JPEG
>>> fail: v4l2-test-formats.cpp(432): testColorspace(pix.pixelformat, pix.colorspace, pix.ycbcr_enc, pix.quantization)
>>
>> The sensor should almost certainly use COLORSPACE_SRGB. Certainly not
>> COLORSPACE_JPEG.
> Ah even for YUYV format, I didn't know ...
The pixel format != colorspace. You can read more about that here, if you are
interested:
https://hverkuil.home.xs4all.nl/spec/media.html#colorspaces
>
>>> Buffer ioctls:
>>> test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: OK
>>> fail: v4l2-test-buffers.cpp(571): q.has_expbuf(node)
>>
>> You are missing .vidioc_expbuf = vbs_ioctl_expbuf and the vb2 io_mode
>> VB2_DMABUF.
> Nope, I have :
> .vidioc_expbuf = vb2_ioctl_expbuf,
> vq->io_modes = VB2_MMAP | VB2_DMABUF;
>
> So it's something more subtle, and I have a bit of work to understand what.
Fix the colorspace issue first, I wonder if it is just fallout from that earlier
issue.
Regards,
Hans
>
> Cheers.
>
> --
> Robert
>
prev parent reply other threads:[~2016-03-21 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 21:01 [PATCH RFC 0/2] pxa_camera transition to v4l2 standalone device Robert Jarzmik
2016-03-19 21:01 ` [PATCH RFC 1/2] media: platform: transfer format translations to soc_mediabus Robert Jarzmik
2016-03-19 21:01 ` [PATCH RFC 2/2] media: platform: pxa_camera: make a standalone v4l2 device Robert Jarzmik
2016-03-21 8:13 ` [PATCH RFC 0/2] pxa_camera transition to v4l2 standalone device Hans Verkuil
2016-03-21 22:26 ` Robert Jarzmik
2016-03-21 22:37 ` Hans Verkuil
2016-03-21 22:42 ` Robert Jarzmik
2016-03-21 22:49 ` Hans Verkuil [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=56F07A90.8060305@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=robert.jarzmik@free.fr \
/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