* [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
@ 2005-10-27 19:30 Kristen Accardi
2005-10-27 19:38 ` Arjan van de Ven
0 siblings, 1 reply; 3+ messages in thread
From: Kristen Accardi @ 2005-10-27 19:30 UTC (permalink / raw)
To: pcihpd-discuss; +Cc: acpi-devel, linux-kernel, rajesh.shah, greg, len.brown
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.
--
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
2005-10-27 19:30 [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev Kristen Accardi
@ 2005-10-27 19:38 ` Arjan van de Ven
2005-10-27 19:46 ` [Pcihpd-discuss] " Matthew Wilcox
0 siblings, 1 reply; 3+ messages in thread
From: Arjan van de Ven @ 2005-10-27 19:38 UTC (permalink / raw)
To: Kristen Accardi
Cc: pcihpd-discuss, acpi-devel, linux-kernel, rajesh.shah, greg,
len.brown
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...
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Pcihpd-discuss] Re: [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
2005-10-27 19:38 ` Arjan van de Ven
@ 2005-10-27 19:46 ` Matthew Wilcox
0 siblings, 0 replies; 3+ messages in thread
From: Matthew Wilcox @ 2005-10-27 19:46 UTC (permalink / raw)
To: Arjan van de Ven
Cc: Kristen Accardi, pcihpd-discuss, acpi-devel, linux-kernel,
rajesh.shah, greg, len.brown
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...
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-10-27 19:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-27 19:30 [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev Kristen Accardi
2005-10-27 19:38 ` Arjan van de Ven
2005-10-27 19:46 ` [Pcihpd-discuss] " Matthew Wilcox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox