From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/6] ARM: OMAP3: PRM: move prcm interrupt handlers to PRM driver code
Date: Tue, 7 Aug 2012 00:28:52 -0700 [thread overview]
Message-ID: <20120807072852.GN11011@atomide.com> (raw)
In-Reply-To: <87ipd4g4a5.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120730 17:36]:
>
> At first, I wasn't sure why this was happening on Overo boards and not
> on the other boards, but then I notcied there was a *lot* more pm_wkup
> interrupts during boot on Overo compared to the other boards. This is
> because of the GPIO IRQ for the network interface as well as the network
> stack itself setting timers, resulting in a lot more pm_wkup events
> during boot and making the race more likely.
Also happens if you may have somehow both edges selected for GPIO
interrupts. Might be worth checking at least just in case of bugs
somewhere..
Tony
next prev parent reply other threads:[~2012-08-07 7:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 16:37 [RFC 0/6] ARM: OMAP3+: minor PM core code cleanup Tero Kristo
2012-07-13 16:37 ` [RFC 1/6] ARM: OMAP3: PRM: move prcm interrupt handlers to PRM driver code Tero Kristo
2012-07-16 11:26 ` Rajendra Nayak
2012-07-16 11:41 ` Tero Kristo
2012-07-31 0:31 ` Kevin Hilman
2012-08-07 7:28 ` Tony Lindgren [this message]
2012-07-13 16:37 ` [RFC 2/6] ARM: OMAP3: clock data: prevent IVA2 DPLL low power stop mode Tero Kristo
2012-07-13 16:37 ` [RFC 3/6] ARM: OMAP3: hwmod data: fix iva2 reset info Tero Kristo
2012-07-16 0:12 ` Paul Walmsley
2012-07-13 16:37 ` [RFC 4/6] ARM: OMAP3: hwmod data: add custom setup_preprogram for iva hwmod Tero Kristo
2012-07-13 16:37 ` [RFC 5/6] ARM: OMAP3: hwmod data: add sad2d hwmod Tero Kristo
2012-07-16 1:14 ` Paul Walmsley
2012-07-16 1:28 ` Paul Walmsley
2012-07-13 16:37 ` [RFC 6/6] ARM: OMAP3: hwmod data: add custom setup_preprogram for " Tero Kristo
2012-07-30 20:53 ` [RFC 0/6] ARM: OMAP3+: minor PM core code cleanup Kevin Hilman
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=20120807072852.GN11011@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).