Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753839Ab1DEWWU (ORCPT ); Tue, 5 Apr 2011 18:22:20 -0400 Received: from mail-iy0-f174.google.com ([209.85.210.174]:64514 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752619Ab1DEWWQ convert rfc822-to-8bit (ORCPT ); Tue, 5 Apr 2011 18:22:16 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=fqWoEW3S7qvR/cbJ1Rd/6JOVtiLaixbg1+tjBzRIGKhkwxq4fUMu+uaiRs+Tjm9lkO 9cDIaLvyl5KoQb6Civ9vbOF0FHvzVuH062eDrzQrEAqFC6PJMPJti4WQ4v1jhSzGI07b jT5WJxPWhtQ2z+7oIlVaVNFqDNf0mkrp0wuCM= MIME-Version: 1.0 In-Reply-To: <4D9AB958.5010304@ti.com> References: <201104031726.37420.arnd@arndb.de> <20110403160324.GA8050@n2100.arm.linux.org.uk> <201104040259.26601.arnd@arndb.de> <1301915022.15819.28.camel@e102109-lin.cambridge.arm.com> <20110404112104.GB19854@n2100.arm.linux.org.uk> <1301923457.417.34.camel@e102391-lin.cambridge.arm.com> <20110404133104.GA23266@n2100.arm.linux.org.uk> <1301925445.417.54.camel@e102391-lin.cambridge.arm.com> <4D9AB958.5010304@ti.com> Date: Wed, 6 Apr 2011 00:22:15 +0200 X-Google-Sender-Auth: dR5Ub8ufxhb5GN_8DzlEX1EV7cM Message-ID: Subject: Re: [GIT PULL] omap changes for v2.6.39 merge window From: Linus Walleij To: Santosh Shilimkar Cc: david@lang.hm, Russell King - ARM Linux , Arnd Bergmann , Nicolas Pitre , Marc Zyngier , Catalin Marinas , lkml , Tony Lindgren , linux-arm-kernel@lists.infradead.org, "H. Peter Anvin" , Thomas Gleixner , linux-omap@vger.kernel.org, Linus Torvalds , Ingo Molnar , Detlef Vollmann , David Brown Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 916 Lines: 21 2011/4/5 Santosh Shilimkar : > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/