Re: [Patch 0/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver

From: Benoit Parrot <bparrot@ti.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: <linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 0/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver
Date: Tue, 23 Jun 2015 14:19:42 -0500	[thread overview]
Message-ID: <20150623191941.GF31636@ti.com> (raw)
In-Reply-To: <5587B9C9.70803@xs4all.nl>

Hans Verkuil <hverkuil@xs4all.nl> wrote on Mon [2015-Jun-22 09:31:21 +0200]:
> On 06/16/2015 07:29 PM, Benoit Parrot wrote:
> > The Camera Adaptation Layer (CAL) is a block which consists of a dual
> > port CSI2/MIPI camera capture engine.
> > This camera engine is currently found on DRA72xx family of devices.
> > 
> > Port #0 can handle CSI2 camera connected to up to 4 data lanes.
> > Port #1 can handle CSI2 camera connected to up to 2 data lanes.
> > 
> > The driver implements the required API/ioctls to be V4L2 compliant.
> > Driver supports the following:
> >     - V4L2 API using DMABUF/MMAP buffer access based on videobuf2 api
> >     - Asynchronous sensor sub device registration
> >     - DT support
> > 
> > Currently each port is designed to connect to a single sub-device.
> > In other words port aggregation is not currently supported.
> > 
> > Here is a sample output of the v4l2-compliance tool:
> > 
> > # ./v4l2-compliance -s -v -d /dev/video0
> 
> Can you show the output of './v4l2-compliance -f' as well?

I can but you won't see much as my test sensor (the only one I have)
only support V4L2_PIX_FMT_SGRBG8.

> 
> Thanks!
> 
> 	Hans
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in