From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH] PM: suspend_device_irqs(): don't disable wakeup IRQs Date: Thu, 07 May 2009 07:13:55 -0700 Message-ID: <87ws8trof0.fsf@deeprootsystems.com> References: <1241483224-7113-1-git-send-email-khilman@deeprootsystems.com> <87y6tb3x6r.fsf@deeprootsystems.com> <871vr22upr.fsf@deeprootsystems.com> <200905062318.23572.rjw@sisk.pl> <87zldpu5rt.fsf@deeprootsystems.com> <4d34a0a70905061828l3e35a954k76967b30c1a241ab@mail.gmail.com> <4d34a0a70905061904w338457efna8a3cbb80537e0c9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from qw-out-2122.google.com ([74.125.92.27]:48587 "EHLO qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756053AbZEGOOB convert rfc822-to-8bit (ORCPT ); Thu, 7 May 2009 10:14:01 -0400 In-Reply-To: <4d34a0a70905061904w338457efna8a3cbb80537e0c9@mail.gmail.com> (Kim Kyuwon's message of "Thu\, 7 May 2009 11\:04\:06 +0900") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Kim Kyuwon Cc: Arve =?iso-8859-1?Q?Hj=F8nnev=E5g?= , "Rafael J. Wysocki" , Andrew Morton , linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Linus Torvalds , Ingo Molnar , OMAP Kim Kyuwon writes: > 2009/5/7 Arve Hj=F8nnev=E5g : >> 2009/5/6 Kim Kyuwon : >>> 2009/5/7 Arve Hj=F8nnev=E5g : >>>> On Wed, May 6, 2009 at 5:16 PM, Kevin Hilman >>>> wrote: >>>>> "Rafael J. Wysocki" writes: >>>>> >>>>>> On Wednesday 06 May 2009, Kevin Hilman wrote: >>>>>>> Kevin Hilman writes: >>>> >>>>> There is at least one problem with that which is why Kyuwon Kim a= dded >>>>> the ->disable hook to OMAP's irq_chip. The problem is with drive= rs >>>>> that call disable_irq() in their suspend hook, usually done to pr= event >>>>> the device from waking the system since on OMAP, any IRQ can be >>>>> configured to wake the system. >>>>> >>>> >>>> This does not sound correct. disable_irq_wake should be used for t= his. >>>> A driver may need to mask its interrupt before suspending but this >>>> should not also disable it as a wakeup source. >>> >>> I wish I could use disable_irq_wake(), but it doesn't work in OMAP. >> >> This does not sound like a hardware problem. > > We may need advices of TI engineers. > However, as far as I know, It is impossible to disable 'interrupt > wake-up' with interrupt enabled. Because an interrupt itself generate > a system wake-up event in OMAP3430 (Hardware level). Interrupt wakeups can be disabled at the PRCM level. Or more simply we can keep a mask of wakeup-enable interrupts and use that. I will experiment with getting disable_irq_wake() working. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html