From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [RFC][PATCH 2/2] PM: Rework handling of interrupts during suspend-resume Date: Thu, 26 Feb 2009 16:27:29 -0800 (PST) Message-ID: References: <200902221837.49396.rjw@sisk.pl> <200902270010.38291.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: =?ISO-8859-15?Q?Arve_Hj=F8nnev=E5g?= Cc: Jeremy Fitzhardinge , LKML , Jesse Barnes , Thomas Gleixner , "Eric W. Biederman" , Ingo Molnar , pm list List-Id: linux-pm@vger.kernel.org On Thu, 26 Feb 2009, Arve Hj=F8nnev=E5g wrote: > = > How many sysdevs use interrupts? > = > I found may drivers in the mainline kernel that use enable_irq_wake, > but I did not see any that handle this race condition. The _only_ driver that does enable_irq_wake() on x86 is the cmos timer = driver, and even there it actually doesn't use irq_wake, but ACPI. Why? = Because I don't think irq wakeup even _works_ on x86. So the whole enable_irq_wake is largely some embedded ARM platform issue, = and a very special case, and doesn't exist anywhere else. Maybe I'm missing something, but it's definitely not the normal case. Linus