All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Enrico <ebutera@users.berlios.de>
Cc: linux-media@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: OMAP3ISP won't start
Date: Mon, 02 Apr 2012 06:45:03 -0600	[thread overview]
Message-ID: <4F799F4F.9020606@mlbassoc.com> (raw)
In-Reply-To: <CA+2YH7svJoCnvUPQGPr=YOsEQBZ16J5y9QGjFyfNmdjeLum4cA@mail.gmail.com>

On 2012-04-02 06:32, Enrico wrote:
> On Mon, Apr 2, 2012 at 2:24 PM, Gary Thomas<gary@mlbassoc.com>  wrote:
>> Just to be clear - I did have to make a few patches to both the
>> TVP5150 driver and CCDC part of OMAP3ISP as some of the BT656
>> support is still not in Laurent's tree.  I'll send patches, etc,
>> once I get it working, but as mentioned above, at least at the
>> register level, these are set up the same as in my working tree.
>
> What patches did you add on top of Laurent tree?
>
> I had a look some days ago and for example it's missing the right
> setup for VD0/VD1 (no VD1 and VD0 set to half height), this could be
> the cause of a not working isp. You can check if you get interrupts
> from the isp (/proc/interrupts).

Getting lots of interrupts:
  24:       3376      INTC  omap-iommu.0, OMAP3 ISP

>
> Another thing that is missing is the logic in the irq handler that
> wait for a complete frame before calling next video buffer (or
> something like that).

The items you mention are just what I merged from my previous kernel.
My changes are still pretty rough but I can send them to you if you'd
like.

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

  reply	other threads:[~2012-04-02 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 12:24 OMAP3ISP won't start Gary Thomas
2012-04-02 12:32 ` Enrico
2012-04-02 12:45   ` Gary Thomas [this message]
2012-04-02 13:15     ` Enrico
2012-04-02 13:31       ` Gary Thomas
2012-04-02 14:38         ` Enrico
2012-04-02 14:55           ` Gary Thomas
2012-04-02 15:51             ` Enrico

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=4F799F4F.9020606@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ebutera@users.berlios.de \
    --cc=laurent.pinchart@ideasonboard.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 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.