Linux Media Controller development
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: javier Martin <javier.martin@vista-silicon.com>,
	linux-media@vger.kernel.org,
	sakari.ailus@maxwell.research.nokia.com,
	kyungmin.park@samsung.com, laurent.pinchart@ideasonboard.com,
	s.hauer@pengutronix.de, p.zabel@pengutronix.de
Subject: Re: [PATCH v6] media: coda: Add driver for Coda video codec.
Date: Mon, 23 Jul 2012 12:21:09 +0200	[thread overview]
Message-ID: <500D2595.7060009@samsung.com> (raw)
In-Reply-To: <201207231214.15835.hverkuil@xs4all.nl>

On 07/23/2012 12:14 PM, Hans Verkuil wrote:
> On Mon July 23 2012 12:00:30 javier Martin wrote:
>> On 23 July 2012 11:45, javier Martin <javier.martin@vista-silicon.com> wrote:
>>> Sorry, I had a problem with my buildroot environment. This is the
>>> v4l2-compliance output with the most recent version:
>>>
>>> # v4l2-compliance -d /dev/video2
>>> Driver Info:
>>>         Driver name   : coda
>>>         Card type     : coda
>>>         Bus info      : coda
>>>         Driver version: 0.0.0
>>>         Capabilities  : 0x84000003
>>>                 Video Capture
>>>                 Video Output
>>>                 Streaming
>>>                 Device Capabilities
>>>         Device Caps   : 0x04000003
>>>                 Video Capture
>>>                 Video Output
>>>                 Streaming
>>>
>>> Compliance test for device /dev/video2 (not using libv4l2):
>>>
>>> Required ioctls:
>>>                 fail: v4l2-compliance.cpp(270): (vcap.version >> 16) < 3
>>>         test VIDIOC_QUERYCAP: FAIL
>>>
>>
>> This was related to a memset() that I did in QUERYCAP.
>>
>> Now the output is cleaner.
> 
> Ah, much better.
> 
>>
>> # v4l2-compliance -d /dev/video2
>> Driver Info:
>>         Driver name   : coda
>>         Card type     : coda
>>         Bus info      : coda
>>         Driver version: 3.5.0
>>         Capabilities  : 0x84000003
>>                 Video Capture
>>                 Video Output
>>                 Streaming
>>                 Device Capabilities
>>         Device Caps   : 0x04000003
>>                 Video Capture
>>                 Video Output
>>                 Streaming
>>
>> Compliance test for device /dev/video2 (not using libv4l2):
>>
>> Required ioctls:
>>         test VIDIOC_QUERYCAP: OK
>>
>> Allow for multiple opens:
>>         test second video open: OK
>>         test VIDIOC_QUERYCAP: OK
>>         test VIDIOC_G/S_PRIORITY: OK
>>
>> Debug ioctls:
>>         test VIDIOC_DBG_G_CHIP_IDENT: Not Supported
>>         test VIDIOC_DBG_G/S_REGISTER: Not Supported
>>         test VIDIOC_LOG_STATUS: Not Supported
>>
>> Input ioctls:
>>         test VIDIOC_G/S_TUNER: Not Supported
>>         test VIDIOC_G/S_FREQUENCY: Not Supported
>>         test VIDIOC_S_HW_FREQ_SEEK: Not Supported
>>         test VIDIOC_ENUMAUDIO: Not Supported
>>         test VIDIOC_G/S/ENUMINPUT: Not Supported
>>         test VIDIOC_G/S_AUDIO: Not Supported
>>         Inputs: 0 Audio Inputs: 0 Tuners: 0
>>
>> Output ioctls:
>>         test VIDIOC_G/S_MODULATOR: Not Supported
>>         test VIDIOC_G/S_FREQUENCY: Not Supported
>>         test VIDIOC_ENUMAUDOUT: Not Supported
>>         test VIDIOC_G/S/ENUMOUTPUT: Not Supported
>>         test VIDIOC_G/S_AUDOUT: Not Supported
>>         Outputs: 0 Audio Outputs: 0 Modulators: 0
>>
>> Control ioctls:
>>         test VIDIOC_QUERYCTRL/MENU: OK
>>         test VIDIOC_G/S_CTRL: OK
>>                 fail: v4l2-test-controls.cpp(565): try_ext_ctrls did
>> not check the read-only flag
> 
> Hmm, what's the reason for this one I wonder. Can you run with '-v2' and see
> for which control this fails?

This might be related to calling video_register_device() with null
ctrl_handler or not setting V4L2_FL_USES_V4L2_FH flags at struct video_device.

--

Regards,
Sylwester




  reply	other threads:[~2012-07-23 10:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 11:08 [PATCH v6] media: coda: Add driver for Coda video codec Javier Martin
2012-07-21  9:46 ` Sakari Ailus
2012-07-23  7:57   ` javier Martin
2012-07-21  9:50 ` Hans Verkuil
2012-07-23  8:02   ` javier Martin
2012-07-23  8:20     ` Hans Verkuil
2012-07-23  8:27       ` javier Martin
2012-07-23  8:36         ` Hans Verkuil
     [not found]           ` <CACKLOr36MnD8fpiJDmDWGir=nWWZEQdrZjvVJTfEBORARMrmGA@mail.gmail.com>
2012-07-23  8:39             ` Fwd: " javier Martin
     [not found]             ` <201207231045.48762.hverkuil@xs4all.nl>
2012-07-23  9:45               ` javier Martin
2012-07-23 10:00                 ` javier Martin
2012-07-23 10:14                   ` Hans Verkuil
2012-07-23 10:21                     ` Sylwester Nawrocki [this message]
2012-07-23 10:33                       ` Hans Verkuil
2012-07-23 10:43                     ` javier Martin
2012-07-23 10:56                       ` Hans Verkuil

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=500D2595.7060009@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=hverkuil@xs4all.nl \
    --cc=javier.martin@vista-silicon.com \
    --cc=kyungmin.park@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=s.hauer@pengutronix.de \
    --cc=sakari.ailus@maxwell.research.nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox