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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 22 Jun 2015 09:31:21 +0200
From:	Hans Verkuil <hverkuil@...all.nl>
To:	Benoit Parrot <bparrot@...com>
CC:	linux-media@...r.kernel.org, devicetree@...r.kernel.org,
	Tony Lindgren <tony@...mide.com>, linux-kernel@...r.kernel.org
Subject: Re: [Patch 0/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver

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?

Thanks!

	Hans

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/