All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: "Weng, Wending" <WWeng@rheinmetall.ca>
Cc: linux-media@vger.kernel.org, "Aguirre Rodriguez,
	Sergio Alberto" <saaguirre@ti.com>
Subject: Re: need help for omap3 isp-camera interface
Date: Tue, 21 Apr 2009 16:48:15 +0300	[thread overview]
Message-ID: <49EDCE9F.2030700@maxwell.research.nokia.com> (raw)
In-Reply-To: <C01FCF206F5D8D4C89B210408D7DB39C29B6BA@mail2.oerlikon.ca>

Weng, Wending wrote:
> Hi All,
> 
> I'm working on video image capture(omap3 isp) interface(PSP 1.0.2),
> and have met many difficulties. At the camera side, the 8 bits BT656
> signal are connected to cam_d[0-7], which looks OK. The cam_fld,
> cam_hs and cam_vs are also connected, At the omap3 side, I use
> saMmapLoopback.c, it runs, however, it receives only HS_VS_IRQ, but
> no any image data. I checked FLDSTAT(CCDC_SYN_MODE), it's never
> changed. Right now, I don't know what to check, if you can give some
> suggestions, your help will be greatly appreciated. Thanks in
> advance.

I haven't been using the parallel interface nor I know anyone else who 
would have. Sergio, any idea?

Anyway, this sounds like a problem in the parallel receiver side. You 
could try also configuring the VD1 IRQ to happen much earlier, say on 
10th line. See ISPCCDC_VDINT handling in ispccdc.c.

I'm going to update the patchset as soon as I get linux-omap booting again.

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com

      parent reply	other threads:[~2009-04-21 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21  3:01 need help for omap3 isp-camera interface Weng, Wending
2009-04-21  4:08 ` Dongsoo, Nathaniel Kim
2009-04-21  4:59 ` Hiremath, Vaibhav
2009-04-21 13:48 ` Sakari Ailus [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=49EDCE9F.2030700@maxwell.research.nokia.com \
    --to=sakari.ailus@maxwell.research.nokia.com \
    --cc=WWeng@rheinmetall.ca \
    --cc=linux-media@vger.kernel.org \
    --cc=saaguirre@ti.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 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.