From: Dirk Behme <dirk.behme@googlemail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Git tree updated to 2.6.19-rc2
Date: Tue, 24 Oct 2006 18:16:53 +0200 [thread overview]
Message-ID: <453E3C75.6060605@gmail.com> (raw)
In-Reply-To: <20061023203925.GC11967@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Tony Lindgren wrote:
> - CONFIG_DEBUG_LL hangs system
For reference see
http://linux.omap.com/pipermail/linux-omap-open-source/2006-October/008025.html
and
http://linux.omap.com/pipermail/linux-omap-open-source/2006-October/008054.html
for an ugly workaround if you really need it. I really have
no clue what is broken here.
> - BUG in omap1_mbox_enable_irq
I think you mean
Unbalanced enable for IRQ 10
BUG: warning at kernel/irq/manage.c:118/enable_irq()
printed in bootmessages.
I spent some minutes for this as well. It is MPU "dsp"
interrupt which is enabled in omap1_mbox_enable_irq() by
enable_irq(mbox->irq);
In kernel/irq/manage.c function enable_irq() checks for
desc->depth and if it is 0 it prints above message. Seems
that desc->depth has to be >= 1.
The comment tells us
* Undoes the effect of one call to disable_irq(). If this
* matches the last disable, processing of interrupts on this
* IRQ line is re-enabled.
so seems that before calling enable_irq() at least one
disable_irq() is needed.
I don't know if patch in attachment is a valid patch or only
a workaround. What do you think?
Best regards
Dirk
[-- Attachment #2: mailbox_irq_patch.txt --]
[-- Type: text/plain, Size: 385 bytes --]
--- arch/arm/plat-omap/mailbox.c_orig 2006-10-24 18:08:06.000000000 +0200
+++ arch/arm/plat-omap/mailbox.c 2006-10-24 18:10:58.000000000 +0200
@@ -237,6 +237,7 @@ static int omap_mbox_init(struct omap_mb
"failed to register mailbox interrupt:%d\n", ret);
goto fail1;
}
+ disable_mbox_irq(mbox, IRQ_RX);
enable_mbox_irq(mbox, IRQ_RX);
spin_lock_init(&mbox->lock);
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-10-24 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 20:39 Git tree updated to 2.6.19-rc2 Tony Lindgren
2006-10-24 7:53 ` Komal Shah
2006-10-28 6:31 ` Aic23 NULL pointer exception, was: " Dirk Behme
2006-10-24 11:05 ` [PATCH] ARM: OMAP: Fixup omap-rtc (was: Git tree updated to 2.6.19-rc2) Jonathan McDowell
2006-10-24 17:57 ` David Brownell
2006-10-27 12:45 ` tony
2006-10-27 16:16 ` omap-keypad issues with 2.6.19-rc? Jonathan McDowell
2006-10-27 16:49 ` [PATCH] ARM: OMAP: Fix Amstrad Delta omap-keypad usage Jonathan McDowell
2006-10-24 16:16 ` Dirk Behme [this message]
2006-10-27 12:50 ` Git tree updated to 2.6.19-rc2 tony
2006-10-27 15:30 ` Dirk Behme
2006-10-29 22:09 ` Hiroshi DOYU
2006-10-26 20:22 ` David Brownell
2006-10-27 12:53 ` tony
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=453E3C75.6060605@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox