From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761956AbZBYQUn (ORCPT ); Wed, 25 Feb 2009 11:20:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753413AbZBYQUc (ORCPT ); Wed, 25 Feb 2009 11:20:32 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:35555 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753249AbZBYQUb (ORCPT ); Wed, 25 Feb 2009 11:20:31 -0500 Date: Wed, 25 Feb 2009 08:19:24 -0800 (PST) From: Linus Torvalds X-X-Sender: torvalds@localhost.localdomain To: Alan Stern cc: "Rafael J. Wysocki" , "Eric W. Biederman" , Jeremy Fitzhardinge , LKML , Jesse Barnes , Thomas Gleixner , Ingo Molnar , pm list Subject: Re: [linux-pm] [RFC][PATCH 2/2] PM: Rework handling of interrupts during suspend-resume In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 25 Feb 2009, Alan Stern wrote: > On Tue, 24 Feb 2009, Rafael J. Wysocki wrote: > > > I think the most important source of level triggered interrupts are PCI > > devices, so perhaps we can make the PCI PM core use bit 10 of the PCI Device > > Control register to prevent devices from generating INTx after the drivers' > > suspend routines have been executed? > > I wish that were true. As I recall, the original PCI specification did > not define this bit, and older PCI devices don't support it. So you > can't count on being able to supress interrupt generation this way. It's definitely a new feature. In fact, I think even the current one makes it optional, so even for "new" devices it's very unclear how many of them actually support that bit. Linus