From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Problems with the omap3isp
Date: Thu, 28 Aug 2014 14:03:27 +0200 [thread overview]
Message-ID: <6301052.X8pjVEUngK@avalon> (raw)
In-Reply-To: <53FDB1EE.6010107@herbrechtsmeier.net>
Hi Stefan,
On Wednesday 27 August 2014 12:24:46 Stefan Herbrechtsmeier wrote:
> Am 04.08.2014 um 17:25 schrieb Laurent Pinchart:
> > On Monday 04 August 2014 11:24:13 Stefan Herbrechtsmeier wrote:
> >> Hi Laurent,
> >>
> >> thank you very much for your help.
> >>
> >> The problem is cross talk on the camera flex cable of the Gumstix Overo.
> >> The XCLKA signal is beside PCLK and VS.
> >
> > Right, I should have mentioned that. It's a know issue, and there's not
> > much that can be done about it without a hardware redesign. A ground (or
> > power supply) signal should really have been inserted on each side of the
> > XCLKA and PCLK signals.
>
> Exists a list about knowing issues with the Gumstix Overo? Because I
> have some problems with the MMC3 too.
Not to my knowledge. This crosstalk issue is something I've discovered and
reported to Gumstix a couple of years ago.
> >> Additionally the OV5647 camera tristate all outputs by default. This
> >> leads to HS_VS_IRQ interrupts.
> >
> > This should be taken care of by pull-up or pull-down resistors on the
> > camera signals. I've disabled them with the Caspa camera given the low
> > drive strength of the buffer on the camera board, but you could enable
> > them on your system.
>
> I have manually rework my camera adapter and change the camera clock
> from XCLKA to XCLKB. Additionally I have enable the pull-ups in my
> device tree. Now the camera sensor from the Raspberry Pi camera module
> works together with the Gumstix Overo.
Great. Any chance to see a driver for the ov5647 being submitted to the linux-
media mailing list ? :-)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-08-28 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 10:04 Problems with the omap3isp Stefan Herbrechtsmeier
2014-07-30 23:10 ` Laurent Pinchart
2014-07-31 8:29 ` Stefan Herbrechtsmeier
2014-08-01 13:57 ` Laurent Pinchart
2014-08-04 9:24 ` Stefan Herbrechtsmeier
2014-08-04 15:25 ` Laurent Pinchart
2014-08-27 10:24 ` Stefan Herbrechtsmeier
2014-08-28 12:03 ` 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=6301052.X8pjVEUngK@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=stefan@herbrechtsmeier.net \
/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