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, 31 Jul 2014 01:10:49 +0200 [thread overview]
Message-ID: <5912662.x67xxWZ5ks@avalon> (raw)
In-Reply-To: <53C4FC99.9050308@herbrechtsmeier.net>
Hi Stefan,
Sorry for the late reply.
On Tuesday 15 July 2014 12:04:09 Stefan Herbrechtsmeier wrote:
> Hi Laurent,
>
> I have some problems with the omap3isp driver. At the moment I use a
> linux-stable 3.14.5 with your fixes for omap3xxx-clocks.dtsi.
>
> 1. If I change the clock rate to 24 MHz in my camera driver the whole
> system freeze at the clk_prepare_enable. The first enable and disable
> works without any problem. The system freeze during a systemd / udev
> call of media-ctl.
I've never seen that before. Where does your sensor get its clock from ? Is it
connected to the ISP XCLKA or XCLKB output ? What happens if you don't change
the clock rate to 24 MHz ? What rate is it set to in that case ?
> 2. If I enable the streaming I get a "omap3isp omap3isp: CCDC won't
> become idle!" and if I disable streaming I get a "omap3isp omap3isp:
> Unable to stop OMAP3 ISP CCDC". I think the problem is, that I can't
> disable the camera output. Do you change the order of the stream enable
> / disable after Linux 3.4?
Not that I know of.
The two problems might be related, maybe we could concentrate on the first one
first.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-07-30 23:10 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 [this message]
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
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=5912662.x67xxWZ5ks@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 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.