From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Михайло Новотний" <michael.novotnuy@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: omap3-isp driver in CSI2 mode
Date: Fri, 20 Jun 2014 10:39:28 +0200 [thread overview]
Message-ID: <3019615.VUrsMMGC6E@avalon> (raw)
In-Reply-To: <CAAT6_75JEX05GYaDni4Z1wuYH5rFRCXnh9SXoc4K+_y2AWR_NQ@mail.gmail.com>
Hi Michael,
On Tuesday 17 June 2014 16:07:20 Михайло Новотний wrote:
> Hi Laurent.
>
> In my case, I don't receive any interrupts from CSI2 module
>
> My post on Ti forum:
> http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/537/p/33699
> 1/1182836.aspx#1182836
Quoting your post:
> I find that I used incorrect data in mux init:
> omap3_mux_init(board_mux, OMAP_PACKAGE_CBB);
> on my board DM3730CBP100,
> I changedmux init to omap3_mux_init(board_mux, OMAP_PACKAGE_CBP);
> Now CSI2 interrupts occur.
>
> But now I have another problem.
> When I start stream, I always recive error:
> [ 83.435546] omap3isp omap3isp: CSI2: ComplexIO Error IRQ 10000
> [ 83.491149] omap3isp omap3isp: CSI2: ComplexIO Error IRQ 30000
> [ 83.544158] omap3isp omap3isp: CSI2: ComplexIO Error IRQ 10000
> [ 83.600830] omap3isp omap3isp: CSI2: ComplexIO Error IRQ 20000
According to the OMAP3 TRM, bits 16 and 17 indicate a control error for lane 2
and 3 respectively. How many lanes does your sensor use, how are they routed,
and how have you specified the OMAP3 ISP platform data in your board file ?
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-06-20 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAT6_74xo5MSxfAVZNHoxXQPMWd_KRWCDTaKvUMx054BD9-9NQ@mail.gmail.com>
2014-06-17 11:15 ` omap3-isp driver in CSI2 mode Laurent Pinchart
[not found] ` <1934518.xtQnOJUCmU@avalon>
[not found] ` <CAAT6_75JEX05GYaDni4Z1wuYH5rFRCXnh9SXoc4K+_y2AWR_NQ@mail.gmail.com>
2014-06-20 8:39 ` Laurent Pinchart [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=3019615.VUrsMMGC6E@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=michael.novotnuy@gmail.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.