All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Dietschi <michael.dietschi@InUnum.com>
To: Enrico <ebutera@users.sourceforge.net>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Sakari Ailus <sakari.ailus@iki.fi>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: omap3isp with DM3730 not working?!
Date: Thu, 31 Jul 2014 14:31:27 +0200	[thread overview]
Message-ID: <53DA371F.9070907@InUnum.com> (raw)
In-Reply-To: <CA+2YH7sROaGEtVLBs9N7FdWG5mzPZDtGgOaD2sgea--kqLELQA@mail.gmail.com>

Am 31.07.2014 12:36, schrieb Enrico:

>
> I think you are missing the ccdc sink pad setup, basically you should
> have something like this:
>
> ....
> - entity 5: OMAP3 ISP CCDC (3 pads, 9 links)
>              type V4L2 subdev subtype Unknown flags 0
>              device node name /dev/v4l-subdev2
>          pad0: Sink
>                  [fmt:UYVY2X8/720x288 field:alternate]
>                  <- "OMAP3 ISP CCP2":1 []
>                  <- "OMAP3 ISP CSI2a":1 []
>                  <- "tvp5150 1-005c":0 [ENABLED]
>          pad1: Source
>                  [fmt:UYVY/720x576 field:interlaced-tb
>                   crop.bounds:(0,0)/720x288
>                   crop:(0,0)/720x288]
>                  -> "OMAP3 ISP CCDC output":0 [ENABLED]
>                  -> "OMAP3 ISP resizer":0 []
>
> with this setup i can correctly capture deinterlaced frames with
> yavta, but have a look at the "[PATCH 00/11] OMAP3 ISP BT.656 support"
> thread, i noticed some problems maybe it's the same for you.
>
> Enrico
>

Hi Enrico,
the setup looks like:

...
- entity 5: OMAP3 ISP CCDC (3 pads, 9 links)

             type V4L2 subdev subtype Unknown flags 0

             device node name /dev/v4l-subdev2

     pad0: Sink

         [fmt:UYVY2X8/720x240 field:alternate]

         <- "OMAP3 ISP CCP2":1 []

         <- "OMAP3 ISP CSI2a":1 []

         <- "tvp5150 3-005c":0 [ENABLED]

     pad1: Source

         [fmt:UYVY/720x240 field:alternate

          crop.bounds:(0,0)/720x240

          crop:(0,0)/720x240]

         -> "OMAP3 ISP CCDC output":0 [ENABLED]

         -> "OMAP3 ISP resizer":0 []

     pad2: Source

         [fmt:unknown/720x239 field:alternate]

         -> "OMAP3 ISP preview":0 []

         -> "OMAP3 ISP AEWB":0 [ENABLED,IMMUTABLE]

         -> "OMAP3 ISP AF":0 [ENABLED,IMMUTABLE]

         -> "OMAP3 ISP histogram":0 [ENABLED,IMMUTABLE]

- entity 6: OMAP3 ISP CCDC output (1 pad, 1 link)

             type Node subtype V4L flags 0

             device node name /dev/video2

     pad0: Sink

         <- "OMAP3 ISP CCDC":1 [ENABLED]

...

- entity 16: tvp5150 3-005c (1 pad, 1 link)

              type V4L2 subdev subtype Unknown flags 0

              device node name /dev/v4l-subdev8

     pad0: Source

         [fmt:UYVY2X8/720x240 field:alternate]

         -> "OMAP3 ISP CCDC":0 [ENABLED]


And I could not find any help in"[PATCH 00/11] OMAP3 ISP BT.656 support"
because it seems that all the mentioned things are already done.

Michael


  reply	other threads:[~2014-07-31 12:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 15:34 omap3isp with DM3730 not working?! Michael Dietschi
2014-07-24 15:57 ` Enrico
2014-07-28  7:20   ` Sakari Ailus
2014-07-28  7:59     ` Michael Dietschi
2014-07-28  8:30     ` Enrico
2014-07-28 10:29       ` Laurent Pinchart
2014-07-28 13:18         ` Enrico
2014-07-29  0:53           ` Laurent Pinchart
2014-07-29 15:38             ` Michael Dietschi
2014-07-30 14:56             ` Michael Dietschi
2014-07-30 15:21               ` Enrico
2014-07-31 10:06                 ` Michael Dietschi
2014-07-31 10:36                   ` Enrico
2014-07-31 12:31                     ` Michael Dietschi [this message]
2014-07-31 13:15                       ` Enrico
2014-07-31 15:49                         ` Michael Dietschi

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=53DA371F.9070907@InUnum.com \
    --to=michael.dietschi@inunum.com \
    --cc=ebutera@users.sourceforge.net \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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.