All of lore.kernel.org
 help / color / mirror / Atom feed
From: Songjun.Wu@microchip.com (Wu, Songjun)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 0/2] [media] atmel-isc: add driver for Atmel ISC
Date: Mon, 15 Aug 2016 15:17:44 +0800	[thread overview]
Message-ID: <5374dc6b-c08d-7ba5-14bb-074075d62277@microchip.com> (raw)
In-Reply-To: <89ed4a10-30d7-87ca-8d9d-22ea2634e4af@xs4all.nl>



On 8/15/2016 15:15, Hans Verkuil wrote:
> On 08/15/2016 08:09 AM, Wu, Songjun wrote:
>>
>>
>> On 8/12/2016 15:32, Hans Verkuil wrote:
>>> 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.
>>>
>> Sorry for the late reply.
>> The subdevice I use supports controls, but I did not develop the v4l2
>> controls in the sensor driver.
>
> So you mean the sensor hardware has controls, but the sensor driver doesn't implement
> them? Do I understand you correctly?
>
Yes, your understanding is correct.

>> Should I add the v4l2 controls and test again?
>
> If the sensor driver does not implement controls (i.e. has a struct v4l2_ctrl_handler),
> then everything is fine and the v4l2-compliance output is correct.
>
> Please confirm this. I just want to be 100% certain about this before I make the pull
> request.
>
I can confirm this. I use the sensor ov7740, and the driver is developed 
by myself, I did not add the v4l2 controls into the sensor driver for now.

> Thanks,
>
> 	Hans
>

WARNING: multiple messages have this Message-ID (diff)
From: "Wu, Songjun" <Songjun.Wu@microchip.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	nicolas.ferre@atmel.com, robh@kernel.org
Cc: laurent.pinchart@ideasonboard.com,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
	"Benoit Parrot" <bparrot@ti.com>,
	linux-kernel@vger.kernel.org,
	"Andrew-CT Chen" <andrew-ct.chen@mediatek.com>,
	"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
	devicetree@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
	"Kamil Debski" <kamil@wypas.org>,
	"Tiffany Lin" <tiffany.lin@mediatek.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Mikhail Ulyanov" <mikhail.ulyanov@cogentembedded.com>,
	"Richard Röjfors" <richard@puffinpack.se>,
	"Hans Verkuil" <hans.verkuil@cisco.com>,
	"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH v9 0/2] [media] atmel-isc: add driver for Atmel ISC
Date: Mon, 15 Aug 2016 15:17:44 +0800	[thread overview]
Message-ID: <5374dc6b-c08d-7ba5-14bb-074075d62277@microchip.com> (raw)
In-Reply-To: <89ed4a10-30d7-87ca-8d9d-22ea2634e4af@xs4all.nl>



On 8/15/2016 15:15, Hans Verkuil wrote:
> On 08/15/2016 08:09 AM, Wu, Songjun wrote:
>>
>>
>> On 8/12/2016 15:32, Hans Verkuil wrote:
>>> 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.
>>>
>> Sorry for the late reply.
>> The subdevice I use supports controls, but I did not develop the v4l2
>> controls in the sensor driver.
>
> So you mean the sensor hardware has controls, but the sensor driver doesn't implement
> them? Do I understand you correctly?
>
Yes, your understanding is correct.

>> Should I add the v4l2 controls and test again?
>
> If the sensor driver does not implement controls (i.e. has a struct v4l2_ctrl_handler),
> then everything is fine and the v4l2-compliance output is correct.
>
> Please confirm this. I just want to be 100% certain about this before I make the pull
> request.
>
I can confirm this. I use the sensor ov7740, and the driver is developed 
by myself, I did not add the v4l2 controls into the sensor driver for now.

> Thanks,
>
> 	Hans
>

WARNING: multiple messages have this Message-ID (diff)
From: "Wu, Songjun" <Songjun.Wu@microchip.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, <nicolas.ferre@atmel.com>,
	<robh@kernel.org>
Cc: laurent.pinchart@ideasonboard.com,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
	"Benoit Parrot" <bparrot@ti.com>,
	linux-kernel@vger.kernel.org,
	"Andrew-CT Chen" <andrew-ct.chen@mediatek.com>,
	"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
	devicetree@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
	"Kamil Debski" <kamil@wypas.org>,
	"Tiffany Lin" <tiffany.lin@mediatek.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Mikhail Ulyanov" <mikhail.ulyanov@cogentembedded.com>,
	"Richard Röjfors" <richard@puffinpack.se>,
	"Hans Verkuil" <hans.verkuil@cisco.com>,
	"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
	"Simon Horman" <horms+renesas@verge.net.au>
Subject: Re: [PATCH v9 0/2] [media] atmel-isc: add driver for Atmel ISC
Date: Mon, 15 Aug 2016 15:17:44 +0800	[thread overview]
Message-ID: <5374dc6b-c08d-7ba5-14bb-074075d62277@microchip.com> (raw)
In-Reply-To: <89ed4a10-30d7-87ca-8d9d-22ea2634e4af@xs4all.nl>



On 8/15/2016 15:15, Hans Verkuil wrote:
> On 08/15/2016 08:09 AM, Wu, Songjun wrote:
>>
>>
>> On 8/12/2016 15:32, Hans Verkuil wrote:
>>> 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.
>>>
>> Sorry for the late reply.
>> The subdevice I use supports controls, but I did not develop the v4l2
>> controls in the sensor driver.
>
> So you mean the sensor hardware has controls, but the sensor driver doesn't implement
> them? Do I understand you correctly?
>
Yes, your understanding is correct.

>> Should I add the v4l2 controls and test again?
>
> If the sensor driver does not implement controls (i.e. has a struct v4l2_ctrl_handler),
> then everything is fine and the v4l2-compliance output is correct.
>
> Please confirm this. I just want to be 100% certain about this before I make the pull
> request.
>
I can confirm this. I use the sensor ov7740, and the driver is developed 
by myself, I did not add the v4l2 controls into the sensor driver for now.

> Thanks,
>
> 	Hans
>

  reply	other threads:[~2016-08-15  7:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11  7:06 [PATCH v9 0/2] [media] atmel-isc: add driver for Atmel ISC Songjun Wu
2016-08-11  7:06 ` Songjun Wu
2016-08-11  7:06 ` Songjun Wu
2016-08-11  7:06 ` [PATCH v9 1/2] [media] atmel-isc: add the Image Sensor Controller code Songjun Wu
2016-08-11  7:06   ` Songjun Wu
2016-08-11  7:06 ` [PATCH v9 2/2] [media] atmel-isc: DT binding for Image Sensor Controller driver Songjun Wu
2016-08-11  7:06   ` Songjun Wu
2016-08-11  7:06   ` Songjun Wu
2016-08-12  7:32 ` [PATCH v9 0/2] [media] atmel-isc: add driver for Atmel ISC Hans Verkuil
2016-08-12  7:32   ` Hans Verkuil
2016-08-12  7:32   ` Hans Verkuil
2016-08-15  6:09   ` Wu, Songjun
2016-08-15  6:09     ` Wu, Songjun
2016-08-15  6:09     ` Wu, Songjun
2016-08-15  7:15     ` Hans Verkuil
2016-08-15  7:15       ` Hans Verkuil
2016-08-15  7:15       ` Hans Verkuil
2016-08-15  7:17       ` Wu, Songjun [this message]
2016-08-15  7:17         ` Wu, Songjun
2016-08-15  7:17         ` Wu, Songjun
2016-08-15  7:34 ` Hans Verkuil
2016-08-15  7:34   ` Hans Verkuil
2016-08-15  7:34   ` Hans Verkuil
2016-08-15  7:47   ` Wu, Songjun
2016-08-15  7:47     ` Wu, Songjun
2016-08-15  7:47     ` Wu, Songjun
2016-08-15 17:24     ` [PATCH] MAINTAINERS: atmel-isc: add entry " Nicolas Ferre
2016-08-15 17:24       ` Nicolas Ferre

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=5374dc6b-c08d-7ba5-14bb-074075d62277@microchip.com \
    --to=songjun.wu@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.