public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Boris Todorov <boris.st.todorov@gmail.com>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: omap3isp: BT.656 support
Date: Tue, 18 Oct 2011 08:07:43 -0600	[thread overview]
Message-ID: <4E9D882F.5010608@mlbassoc.com> (raw)
In-Reply-To: <CAFYgh7z4r+oZg4K7Zh6-CTm2Th9RNujOS-b8W_qb-C8q9LRr2w@mail.gmail.com>

On 2011-10-18 07:33, Boris Todorov wrote:
> Hi
>
> I'm trying to run OMAP + TVP5151 in BT656 mode.
>
> I'm using omap3isp-omap3isp-yuv (git.linuxtv.org/pinchartl/media.git).
> Plus the following patches:
>
> TVP5151:
> https://github.com/ebutera/meta-igep/tree/testing-v2/recipes-kernel/linux/linux-3.0+3.1rc/tvp5150
>
> The latest RFC patches for BT656 support:
>
> Enrico Butera (2):
>    omap3isp: ispvideo: export isp_video_mbus_to_pix
>    omap3isp: ispccdc: configure CCDC registers and add BT656 support
>
> Javier Martinez Canillas (1):
>    omap3isp: ccdc: Add interlaced field mode to platform data
>
>
> I'm able to configure with media-ctl:
>
> media-ctl -v -r -l '"tvp5150 3-005c":0->"OMAP3 ISP CCDC":0[1], "OMAP3
> ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]'
> media-ctl -v --set-format '"tvp5150 3-005c":0 [UYVY2X8 720x525]'
> media-ctl -v --set-format '"OMAP3 ISP CCDC":0 [UYVY2X8 720x525]'
> media-ctl -v --set-format '"OMAP3 ISP CCDC":1 [UYVY2X8 720x525]'
>
> But
> ./yavta -f UYVY -s 720x525 -n 4 --capture=4 -F /dev/video4
>
> sleeps after
> ...
> Buffer 1 mapped at address 0x4021d000.
> length: 756000 offset: 1515520
> Buffer 2 mapped at address 0x402d6000.
> length: 756000 offset: 2273280
> Buffer 3 mapped at address 0x4038f000.
>
> Anyone with the same issue??? This happens with every other v4l test app I used.
> I can see data from TVP5151 but there are no interrupts in ISP.

Why are you using /dev/video4?  The CCDC output is on /dev/video2

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2011-10-18 14:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 13:33 omap3isp: BT.656 support Boris Todorov
2011-10-18 14:07 ` Gary Thomas [this message]
2011-10-18 14:28   ` Boris Todorov
2011-10-18 14:49     ` Gary Thomas
2011-10-18 15:10       ` Boris Todorov
2011-10-18 15:24         ` Gary Thomas
2011-10-18 15:53           ` Boris Todorov
2011-10-18 16:04             ` Gary Thomas
2011-10-18 16:14               ` Boris Todorov
2011-10-18 16:24                 ` Gary Thomas
2011-10-18 16:31 ` Enrico
2011-10-19  7:01   ` Boris Todorov
2011-10-19  8:28     ` Enrico
2011-10-19  9:03       ` Boris Todorov
2011-10-19 12:40         ` Enrico
2011-10-19 13:06           ` Boris Todorov
2011-10-19 15:56             ` Boris Todorov
2011-10-19 16:26 ` Stefan Herbrechtsmeier
     [not found]   ` <CAFYgh7xxCM0=hiU9+bFS+qA447wC4+OkCRxv1eonYMgTH7oeEw@mail.gmail.com>
2011-10-20  9:03     ` Stefan Herbrechtsmeier
2011-10-20 12:14       ` Boris Todorov
2011-10-20 14:36         ` Stefan Herbrechtsmeier
2011-10-23 19:15           ` Boris Todorov
2011-10-24  9:47             ` Gary Thomas
2011-10-24 10:33               ` Boris Todorov

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=4E9D882F.5010608@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=boris.st.todorov@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /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