Re: [PATCHv2] [media] rcar-vin: add Renesas R-Car VIN driver

[Hans Verkuil <hverkuil@xs4all.nl>]

On 02/27/2016 06:21 PM, Niklas Söderlund wrote:
> Hi Hans,
> 
> On 2016-02-27 12:32:14 +0100, Hans Verkuil wrote:
>> On 02/24/2016 03:58 AM, Niklas Söderlund wrote:
>>> A V4L2 driver for Renesas R-Car VIN driver that do not depend on
>>> soc_camera. The driver is heavily based on its predecessor and aims to
>>> replace it.
>>>
>>> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>>> ---
>>>
>>> The driver is tested on Koelsch and can do streaming using qv4l2 and
>>> grab frames using yavta. It passes a v4l2-compliance (git master) run
>>> without failures, see bellow for output. Some issues I know about but
>>> will have to wait for future work in other patches.
>>>  - The soc_camera driver provides some pixel formats that do not display
>>>    properly for me in qv4l2 or yavta. I have ported these formats as is
>>>    (not working correctly?) to the new driver.
>>>  - One can not bind/unbind the subdevice and continue using the driver.
>>>
>>> As stated in commit message the driver is based on its soc_camera
>>> version but some features have been drooped (for now?).
>>>  - The driver no longer try to use the subdev for cropping (using
>>>    cropcrop/s_crop).
>>>  - Do not interrogate the subdev using g_mbus_config.
>>
>> A quick question: was this tested with the adv7180 only? Or do you also
>> have access to a sensor to test with?
> 
> I'm not sure I understand your question. I have only tested on Koelsch 
> with a adv7180 connected to the VIN. But I have had both a NTSC camera 
> and a PAL Super Nintendo connected to the Koelsch (adv7180).

OK, that's what I was looking for. I believe it is possible to connect an
external camera sensor as well to the board, so I was just wondering if you
had perhaps done that. But that's clearly not the case.

No problem, I was just curious.

Regards,

	Hans