devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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

      reply	other threads:[~2015-06-23 19:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 17:29 [Patch 0/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver Benoit Parrot
2015-06-16 17:29 ` [Patch 1/2] " Benoit Parrot
2015-06-22  8:09   ` Hans Verkuil
2015-06-23 19:36     ` Benoit Parrot
2015-09-16 21:22       ` Benoit Parrot
     [not found] ` <1434475763-20294-1-git-send-email-bparrot-l0cyMroinI0@public.gmane.org>
2015-06-16 17:29   ` [Patch 2/2] media: v4l: ti-vpe: Document CAL driver Benoit Parrot
2015-06-22  7:31   ` [Patch 0/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver Hans Verkuil
2015-06-23 19:19     ` Benoit Parrot [this message]

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=20150623191941.GF31636@ti.com \
    --to=bparrot@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=tony@atomide.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).