linux-toradex.git/drivers/pci/Kconfig, branch v2.6.34.8

PCI: push deprecated pci_find_device() function to last user

2010-02-23T00:17:01+00:00

The ISDN4Linux HiSax driver family contains the last remaining users
of the deprecated pci_find_device() function. This patch creates a
private copy of that function in HiSax, and removes the now unused
global function together with its controlling configuration option,
CONFIG_PCI_LEGACY.

Signed-off-by: Tilman Schmidt 
Signed-off-by: Jesse Barnes

PCI: remove pci_find_slot from PCI_LEGACY config description

2009-11-04T21:06:42+00:00

Commit 3b073eda has removed pci_find_slot, so there's no point in
mentioning it in the config description as one of the deprecated APIs
there are enabled by PCI_LEGACY and still used by some drivers.

Signed-off-by: Thadeu Lima de Souza Cascardo 
Signed-off-by: Jesse Barnes

PCI hotplug: move IOAPIC support from acpiphp to ioapic driver

2009-11-04T21:06:39+00:00

This patch moves PCI I/O APIC support from acpiphp to a separate driver.

Like pciehp and shpchp, acpiphp handles PCI hotplug, i.e., addition and
removal of PCI adapters.  But in addition, acpiphp handles some ACPI
hotplug, such as the addition of new host bridges, and the I/O APIC
support was tangled up with that.

I don't think the I/O APIC support needs to be in acpiphp; PCI I/O APICs
usually appear as a function on a PCI host bridge, and we'll enumerate the
APIC before any of the devices behind the bridge that use it.

As far as I know, nobody actually uses I/O APIC hotplug.  It depends on
acpi_register_ioapic(), which is only implemented for ia64, and I don't
think any vendors have supported I/O chassis hotplug yet.

Signed-off-by: Bjorn Helgaas 
Reviewed-by: Kenji Kaneshige 
CC: Satoru Takeuchi 
CC: MUNEDA Takahiro 
Signed-off-by: Jesse Barnes

PCI: initialize and release SR-IOV capability

2009-03-20T17:48:22+00:00

If a device has the SR-IOV capability, initialize it (set the ARI
Capable Hierarchy in the lowest numbered PF if necessary; calculate
the System Page Size for the VF MMIO, probe the VF Offset, Stride
and BARs). A lock for the VF bus allocation is also initialized if
a PF is the lowest numbered PF.

Reviewed-by: Matthew Wilcox 
Signed-off-by: Yu Zhao 
Signed-off-by: Jesse Barnes

PCI: pci-stub module to reserve pci device

2009-01-07T19:12:38+00:00

When doing device assignment with KVM there's currently nothing to
protect the device from having a driver in the host as well as the guest.
This trivial module just binds the pci device on the host to a stub
driver so that a real host driver can't bind to the device.  It has no
pci id table, it supports only dynamic ids.

 # echo "8086 10f5" > /sys/bus/pci/drivers/pci-stub/new_id
 # echo -n 0000:00:19.0 > /sys/bus/pci/drivers/e1000e/unbind
 # echo -n 0000:00:19.0 > /sys/bus/pci/drivers/pci-stub/bind
 # ls -l /sys/bus/pci/devices/0000:00:19.0/driver
 lrwxrwxrwx 1 root root 0 2008-11-25 19:10 /sys/bus/pci/devices/0000:00:19.0/driver -> ../../../bus/pci/drivers/pci-stub

Cc: "Kay, Allen M" 
Cc: "Nakajima, Jun" 
Signed-off-by: Chris Wright 
Acked-by: Greg Kroah-Hartman 
Signed-off-by: Jesse Barnes

PCI: Add Kconfig option to disable deprecated pci_find_* API

2007-11-05T21:35:17+00:00

Signed-off-by: Jeff Garzik 
Signed-off-by: Greg Kroah-Hartman

PCI: remove the broken PCI_MULTITHREAD_PROBE option

2007-05-03T02:02:38+00:00

This patch removes the PCI_MULTITHREAD_PROBE option that had already 
been marked as broken.

Signed-off-by: Adrian Bunk 
Signed-off-by: Greg Kroah-Hartman

msi: introduce ARCH_SUPPORTS_MSI Kconfig option (rev2)

2007-05-03T02:02:37+00:00

Allows architectures to advertise that they support MSI rather than listing
each architecture as a PCI_MSI dependency.

Signed-off-by: Dan Williams 
Acked-by: "Eric W. Biederman" 
Signed-off-by: Greg Kroah-Hartman

[SPARC64]: Add PCI MSI support on Niagara.

2007-02-11T07:50:37+00:00

This is kind of hokey, we could use the hardware provided facilities
much better.

MSIs are assosciated with MSI Queues.  MSI Queues generate interrupts
when any MSI assosciated with it is signalled.  This suggests a
two-tiered IRQ dispatch scheme:

	MSI Queue interrupt --> queue interrupt handler
		MSI dispatch --> driver interrupt handler

But we just get one-level under Linux currently.  What I'd like to do
is possibly stick the IRQ actions into a per-MSI-Queue data structure,
and dispatch them form there, but the generic IRQ layer doesn't
provide a way to do that right now.

So, the current kludge is to "ACK" the interrupt by processing the
MSI Queue data structures and ACK'ing them, then we run the actual
handler like normal.

We are wasting a lot of useful information, for example the MSI data
and address are provided with ever MSI, as well as a system tick if
available.  If we could pass this into the IRQ handler it could help
with certain things, in particular for PCI-Express error messages.

The MSI entries on sparc64 also tell you exactly which bus/device/fn
sent the MSI, which would be great for error handling when no
registered IRQ handler can service the interrupt.

We override the disable/enable IRQ chip methods in sun4v_msi, so we
have to call {mask,unmask}_msi_irq() directly from there.  This is
another ugly wart.

Signed-off-by: David S. Miller

[PATCH] PCI: disable PCI_MULTITHREAD_PROBE

2007-01-05T20:33:05+00:00

Unfortunatly, no one reads Kconfig help entries :(

Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman