[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0902261620370.3111@localhost.localdomain>
Date: Thu, 26 Feb 2009 16:27:29 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Arve Hjønnevåg <arve@...roid.com>
cc: "Rafael J. Wysocki" <rjw@...k.pl>, Ingo Molnar <mingo@...e.hu>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
LKML <linux-kernel@...r.kernel.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Jeremy Fitzhardinge <jeremy@...p.org>,
pm list <linux-pm@...ts.linux-foundation.org>,
Len Brown <lenb@...nel.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC][PATCH 2/2] PM: Rework handling of interrupts during
suspend-resume
On Thu, 26 Feb 2009, Arve Hjønnevåg 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
--
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