From: Jonathan Cameron <jic23@cam.ac.uk>
To: Linux Media Mailing List <linux-media@vger.kernel.org>,
laurent.pinchart@ideasonboard.com
Subject: omap3isp: known causes of "CCDC won't become idle!
Date: Tue, 05 Jul 2011 12:22:06 +0100 [thread overview]
Message-ID: <4E12F3DE.5030109@cam.ac.uk> (raw)
Hi Laurent,
I'm just trying to get an mt9v034 sensor working on a beagle xm.
Everything more or less works, except that after a random number
of frames of capture, I tend to get won't become idle messages
and the vd0 and vd1 interrupts tend to turn up at same time.
I was just wondering if there are any known issues with the ccdc
driver / silicon that might explain this?
I also note that it appears to be impossible to disable HS_VS_IRQ
despite the datasheet claiming this can be done. Is this a known
issue?
Thanks,
Jonathan
next reply other threads:[~2011-07-05 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 11:22 Jonathan Cameron [this message]
2011-07-05 12:19 ` omap3isp: known causes of "CCDC won't become idle! Sakari Ailus
2011-07-05 12:25 ` Laurent Pinchart
2011-07-05 13:48 ` Jonathan Cameron
2011-07-05 14:38 ` Sakari Ailus
2011-07-05 15:02 ` Laurent Pinchart
2011-07-05 15:22 ` Jonathan Cameron
2011-07-05 16:35 ` Jonathan Cameron
2011-07-06 16:30 ` Jonathan Cameron
2011-07-05 16:16 ` Sakari Ailus
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=4E12F3DE.5030109@cam.ac.uk \
--to=jic23@cam.ac.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox