[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTins_YaNYSRc1ryZuRSnGKO2MEemuA@mail.gmail.com>
Date: Wed, 6 Apr 2011 00:22:15 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Santosh Shilimkar <santosh.shilimkar@...com>
Cc: david@...g.hm, Russell King - ARM Linux <linux@....linux.org.uk>,
Arnd Bergmann <arnd@...db.de>,
Nicolas Pitre <nico@...xnic.net>,
Marc Zyngier <Marc.Zyngier@....com>,
Catalin Marinas <catalin.marinas@....com>,
lkml <linux-kernel@...r.kernel.org>,
Tony Lindgren <tony@...mide.com>,
linux-arm-kernel@...ts.infradead.org,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-omap@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, Detlef Vollmann <dv@...lmann.ch>,
David Brown <davidb@...eaurora.org>
Subject: Re: [GIT PULL] omap changes for v2.6.39 merge window
2011/4/5 Santosh Shilimkar <santosh.shilimkar@...com>:
> The only issue I see is the clock-events implemented using
> local timers capabilities in low power modes. The local timers
> won't be able wakeup CPU from DORMANT or OFF state and hence
> you will need an additional wakeup capable clock-event
> working together with the local timers using clock-notifiers.
And this is because the IRQs it emits are local and thus cannot wake
the system? This sounds way backwards... A simple naïve solution
would have been to just route out an external IRQ line back from a
selected timer and into the GIC so it will be able to wake up the
system, right?
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists