[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c6593866-db70-b2a6-ee5a-32b6fecc3775@xs4all.nl>
Date: Fri, 12 Aug 2016 09:32:42 +0200
From: Hans Verkuil <hverkuil@...all.nl>
To: Songjun Wu <songjun.wu@...rochip.com>, nicolas.ferre@...el.com,
robh@...nel.org
Cc: laurent.pinchart@...asonboard.com,
linux-arm-kernel@...ts.infradead.org, linux-media@...r.kernel.org,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Arnd Bergmann <arnd@...db.de>,
Niklas Söderlund
<niklas.soderlund+renesas@...natech.se>,
Benoit Parrot <bparrot@...com>, linux-kernel@...r.kernel.org,
Andrew-CT Chen <andrew-ct.chen@...iatek.com>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
devicetree@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Kamil Debski <kamil@...as.org>,
Tiffany Lin <tiffany.lin@...iatek.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Mark Rutland <mark.rutland@....com>,
Mikhail Ulyanov <mikhail.ulyanov@...entembedded.com>,
Richard Röjfors <richard@...finpack.se>,
Hans Verkuil <hans.verkuil@...co.com>,
Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>,
Simon Horman <horms+renesas@...ge.net.au>
Subject: Re: [PATCH v9 0/2] [media] atmel-isc: add driver for Atmel ISC
One quick question:
On 08/11/2016 09:06 AM, Songjun Wu wrote:
> The Image Sensor Controller driver includes two parts.
> 1) Driver code to implement the ISC function.
> 2) Device tree binding documentation, it describes how
> to add the ISC in device tree.
>
> Test result with v4l-utils.
> # v4l2-compliance -f
> v4l2-compliance SHA : not available
>
> Driver Info:
> Driver name : atmel_isc
> Card type : Atmel Image Sensor Controller
> Bus info : platform:atmel_isc f0008000.isc
> Driver version: 4.7.0
> Capabilities : 0x84200001
> Video Capture
> Streaming
> Extended Pix Format
> Device Capabilities
> Device Caps : 0x04200001
> Video Capture
> Streaming
> Extended Pix Format
>
> Compliance test for device /dev/video0 (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
> test for unlimited opens: OK
>
> Debug ioctls:
> test VIDIOC_DBG_G/S_REGISTER: OK (Not Supported)
> test VIDIOC_LOG_STATUS: OK (Not Supported)
>
> 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)
> test VIDIOC_G/S/ENUMINPUT: OK
> test VIDIOC_G/S_AUDIO: OK (Not Supported)
> Inputs: 1 Audio Inputs: 0 Tuners: 0
>
> Output ioctls:
> test VIDIOC_G/S_MODULATOR: OK (Not Supported)
> test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
> test VIDIOC_ENUMAUDOUT: OK (Not Supported)
> test VIDIOC_G/S/ENUMOUTPUT: OK (Not Supported)
> test VIDIOC_G/S_AUDOUT: OK (Not Supported)
> Outputs: 0 Audio Outputs: 0 Modulators: 0
>
> Input/Output configuration ioctls:
> test VIDIOC_ENUM/G/S/QUERY_STD: OK (Not Supported)
> test VIDIOC_ENUM/G/S/QUERY_DV_TIMINGS: OK (Not Supported)
> test VIDIOC_DV_TIMINGS_CAP: OK (Not Supported)
> test VIDIOC_G/S_EDID: OK (Not Supported)
>
> Test input 0:
>
> Control ioctls:
> test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: OK (Not Supported)
> test VIDIOC_QUERYCTRL: OK (Not Supported)
> test VIDIOC_G/S_CTRL: OK (Not Supported)
> test VIDIOC_G/S/TRY_EXT_CTRLS: OK (Not Supported)
> test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: OK (Not Supported)
> test VIDIOC_G/S_JPEGCOMP: OK (Not Supported)
> Standard Controls: 0 Private Controls: 0
Can you confirm that the sensor subdevice you are using does not have any controls?
I ask since that is fairly unusual, so I want to make sure that controls are really
not supported in this setup.
Regards,
Hans
Powered by blists - more mailing lists