From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, khilman@deeprootsystems.com
Subject: Re: Bug in linux omap clock framework?
Date: Tue, 09 Dec 2008 11:15:00 +0200 [thread overview]
Message-ID: <1228814100.8668.100.camel@tubuntu> (raw)
In-Reply-To: <alpine.DEB.2.00.0812061635110.21247@utopia.booyaka.com>
On Sat, 2008-12-06 at 16:51 -0700, ext Paul Walmsley wrote:
> Hi Tomi,
>
> nice test case.
>
> On Fri, 5 Dec 2008, Tomi.Valkeinen@nokia.com wrote:
>
> > I have had strange clk_enable() crashes with DSS2, and now I managed to
> > isolate it. With the included patch, on OMAP3 SDP board, with default
> > kernel config, I always get the crash below. In this example case it
> > happens at specific time on boot, but with DSS2 it happens randomly at
> > runtime, when I enable the DSS clocks.
>
> Looks like there's some problem with the DSS driver's usage of
> dss_tv_fclk. Enabling dss_tv_fclk before entering your test code's
> while-loop makes the problem go away here. Patch below.
>
> As an aside, your test patch does not actually disable dss1_fclk, since it
> is already enabled by the time the while-loop starts. So you might also
> want to add a clk_disable(c2) before your while-loop starts, when you
> test.
>
> Based on the traceback that you sent, I'd conjecture that probably some
> part of the DSS subsystem is generating an interrupt via DSS_IRQ; but then
> dss_iclk ends up disabled, and the MPU INTC is not able to communicate
> with the DSS, and the INTC wedges. (The aborting access is to 0xd8200098,
> the INTCPS_PENDING_IRQ0 register, rather than a DSS register.) Probably
> some IRQs need to be masked before disabling the dss_iclk.
It doesn't seem to be DSS related, the same crash happens also with
cam_ick and sgx_ick.
Tomi
prev parent reply other threads:[~2008-12-09 9:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:49 Bug in linux omap clock framework? Tomi.Valkeinen
2008-12-05 18:23 ` Kevin Hilman
2008-12-08 7:59 ` Tomi Valkeinen
2008-12-06 23:51 ` Paul Walmsley
2008-12-08 8:59 ` Tomi Valkeinen
2008-12-08 9:24 ` Paul Walmsley
2008-12-08 9:36 ` Tomi Valkeinen
2008-12-09 13:58 ` Tomi Valkeinen
2008-12-09 23:14 ` Paul Walmsley
2008-12-10 3:04 ` Igor Stoppa
2008-12-10 7:02 ` Paul Walmsley
2008-12-10 7:37 ` Högander Jouni
2008-12-10 7:59 ` Tomi Valkeinen
2008-12-10 8:44 ` Högander Jouni
2008-12-10 8:57 ` Tomi Valkeinen
2008-12-10 10:44 ` Högander Jouni
2008-12-10 11:53 ` Tomi Valkeinen
2008-12-11 9:19 ` Högander Jouni
2008-12-11 16:17 ` Paul Walmsley
2008-12-12 7:48 ` Tomi Valkeinen
2008-12-09 9:15 ` Tomi Valkeinen [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=1228814100.8668.100.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.