Date: Thu, 27 Oct 2005 13:46:11 -0600
From: Matthew Wilcox <matthew@wil.cx>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Kristen Accardi <kristen.c.accardi@intel.com>,
       pcihpd-discuss@lists.sourceforge.net, acpi-devel@lists.sourceforge.net,
       linux-kernel@vger.kernel.org, rajesh.shah@intel.com, greg@kroah.com,
       len.brown@intel.com
Subject: Re: [Pcihpd-discuss] Re: [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
Message-ID: <20051027194611.GC8201@parisc-linux.org>
References: <1130441405.5996.23.camel@whizzy> <1130441897.3027.18.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1130441897.3027.18.camel@laptopd505.fenrus.org>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 940
Lines: 17

On Thu, Oct 27, 2005 at 09:38:17PM +0200, Arjan van de Ven wrote:
> On Thu, 2005-10-27 at 12:30 -0700, Kristen Accardi wrote:
> > Store the value of PCI_INTERRUPT_PIN in the pci_dev structure for use
> > later.  This is useful for pci hotplug.  When a device is "surprise"
> > removed, the pci config space is no longer available.  However,
> > the pin value is needed to correctly disable the irq for the device.
> 
> Hmmm maybe it's just me..... but... isn't that both advisory and
> entirely unrelated to any kind of real interrupt thing? Eg dev->irq is
> there already and works even in the sight of IO-APICs etc etc...

With surprise hotplug, we can't read the pin from the card any more...
-
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/