rt = (struct irq_routing_table *)addr; if (rt->signature != PIRQ_SIGNATURE ||
rt->version != PIRQ_VERSION ||
rt->size % 16 ||
rt->size < sizeof(struct irq_routing_table) ||
(limit && rt->size > limit - addr)) return NULL;
sum = 0; for (i = 0; i < rt->size; i++)
sum += addr[i]; if (!sum) {
DBG(KERN_DEBUG "PCI: Interrupt Routing Table found at 0x%lx\n",
__pa(rt)); return rt;
} return NULL;
}
/* * Handle the $IRT PCI IRQ Routing Table format used by AMI for its BCP * (BIOS Configuration Program) external tool meant for tweaking BIOS * structures without the need to rebuild it from sources. The $IRT * format has been invented by AMI before Microsoft has come up with its * $PIR format and a $IRT table is therefore there in some systems that * lack a $PIR table. * * It uses the same PCI BIOS 2.1 format for interrupt routing entries * themselves but has a different simpler header prepended instead, * occupying 8 bytes, where a `$IRT' signature is followed by one byte * specifying the total number of interrupt routing entries allocated in * the table, then one byte specifying the actual number of entries used * (which the BCP tool can take advantage of when modifying the table), * and finally a 16-bit word giving the IRQs devoted exclusively to PCI. * Unlike with the $PIR table there is no alignment guarantee. * * Given the similarity of the two formats the $IRT one is trivial to * convert to the $PIR one, which we do here, except that obviously we * have no information as to the router device to use, but we can handle * it by matching PCI device IDs actually seen on the bus against ones * that our individual routers recognise. * * Reportedly there is another $IRT table format where a 16-bit word * follows the header instead that points to interrupt routing entries * in a $PIR table provided elsewhere. In that case this code will not * be reached though as the $PIR table will have been chosen instead.
*/ staticinlinestruct irq_routing_table *pirq_convert_irt_table(u8 *addr,
u8 *limit)
{ struct irt_routing_table *ir; struct irq_routing_table *rt;
u16 size;
u8 sum; int i;
ir = (struct irt_routing_table *)addr; if (ir->signature != IRT_SIGNATURE || !ir->used || ir->size < ir->used) return NULL;
if (pirq_table_addr) {
rt = pirq_check_routing_table((u8 *)__va(pirq_table_addr),
NULL); if (rt) return rt;
printk(KERN_WARNING "PCI: PIRQ table NOT found at pirqaddr\n");
} for (addr = bios_start;
addr < bios_end - sizeof(struct irq_routing_table);
addr += 16) {
rt = pirq_check_routing_table(addr, bios_end); if (rt) return rt;
} for (addr = bios_start;
addr < bios_end - sizeof(struct irt_routing_table);
addr++) {
rt = pirq_convert_irt_table(addr, bios_end); if (rt) return rt;
} return NULL;
}
/* * If we have a IRQ routing table, use it to search for peer host * bridges. It's a gross hack, but since there are no other known * ways how to get a list of buses, we have to go this way.
*/
/* * PIRQ routing for the M1487 ISA Bus Controller (IBC) ASIC used * with the ALi FinALi 486 chipset. The IBC is not decoded in the * PCI configuration space, so we identify it by the accompanying * M1489 Cache-Memory PCI Controller (CMP) ASIC. * * There are four 4-bit mappings provided, spread across two PCI * INTx Routing Table Mapping Registers, available in the port I/O * space accessible indirectly via the index/data register pair at * 0x22/0x23, located at indices 0x42 and 0x43 for the INT1/INT2 * and INT3/INT4 lines respectively. The INT1/INT3 and INT2/INT4 * lines are mapped in the low and the high 4-bit nibble of the * corresponding register as follows: * * 0000 : Disabled * 0001 : IRQ9 * 0010 : IRQ3 * 0011 : IRQ10 * 0100 : IRQ4 * 0101 : IRQ5 * 0110 : IRQ7 * 0111 : IRQ6 * 1000 : Reserved * 1001 : IRQ11 * 1010 : Reserved * 1011 : IRQ12 * 1100 : Reserved * 1101 : IRQ14 * 1110 : Reserved * 1111 : IRQ15 * * In addition to the usual ELCR register pair there is a separate * PCI INTx Sensitivity Register at index 0x44 in the same port I/O * space, whose bits 3:0 select the trigger mode for INT[4:1] lines * respectively. Any bit set to 1 causes interrupts coming on the * corresponding line to be passed to ISA as edge-triggered and * otherwise they are passed as level-triggered. Manufacturer's * documentation says this register has to be set consistently with * the relevant ELCR register. * * Accesses to the port I/O space concerned here need to be unlocked * by writing the value of 0xc5 to the Lock Register at index 0x03 * beforehand. Any other value written to said register prevents * further accesses from reaching the register file, except for the * Lock Register being written with 0xc5 again. * * References: * * "M1489/M1487: 486 PCI Chip Set", Version 1.2, Acer Laboratories * Inc., July 1997
*/
/* * ALI pirq entries are damn ugly, and completely undocumented. * This has been figured out from pirq tables, and it's not a pretty * picture.
*/ staticint pirq_ali_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{ staticconstunsignedchar irqmap[16] = { 0, 9, 3, 10, 4, 5, 7, 6, 1, 11, 0, 12, 0, 14, 0, 15 };
/* * PIRQ routing for the 82374EB/82374SB EISA System Component (ESC) * ASIC used with the Intel 82420 and 82430 PCIsets. The ESC is not * decoded in the PCI configuration space, so we identify it by the * accompanying 82375EB/82375SB PCI-EISA Bridge (PCEB) ASIC. * * There are four PIRQ Route Control registers, available in the * port I/O space accessible indirectly via the index/data register * pair at 0x22/0x23, located at indices 0x60/0x61/0x62/0x63 for the * PIRQ0/1/2/3# lines respectively. The semantics is the same as * with the PIIX router. * * Accesses to the port I/O space concerned here need to be unlocked * by writing the value of 0x0f to the ESC ID Register at index 0x02 * beforehand. Any other value written to said register prevents * further accesses from reaching the register file, except for the * ESC ID Register being written with 0x0f again. * * References: * * "82374EB/82374SB EISA System Component (ESC)", Intel Corporation, * Order Number: 290476-004, March 1996 * * "82375EB/82375SB PCI-EISA Bridge (PCEB)", Intel Corporation, Order * Number: 290477-004, March 1996
*/
/* * The Intel PIIX4 pirq rules are fairly simple: "pirq" is * just a pointer to the config space.
*/ staticint pirq_piix_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{
u8 x;
staticint pirq_piix_set(struct pci_dev *router, struct pci_dev *dev, int pirq, int irq)
{
pci_write_config_byte(router, pirq, irq); return 1;
}
/* * PIRQ routing for the 82426EX ISA Bridge (IB) ASIC used with the * Intel 82420EX PCIset. * * There are only two PIRQ Route Control registers, available in the * combined 82425EX/82426EX PCI configuration space, at 0x66 and 0x67 * for the PIRQ0# and PIRQ1# lines respectively. The semantics is * the same as with the PIIX router. * * References: * * "82420EX PCIset Data Sheet, 82425EX PCI System Controller (PSC) * and 82426EX ISA Bridge (IB)", Intel Corporation, Order Number: * 290488-004, December 1995
*/
#define PCI_I82426EX_PIRQ_ROUTE_CONTROL 0x66u
staticint pirq_ib_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{ int reg;
u8 x;
/* * The VIA pirq rules are nibble-based, like ALI, * but without the ugly irq number munging. * However, PIRQD is in the upper instead of lower 4 bits.
*/ staticint pirq_via_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{ return read_config_nybble(router, 0x55, pirq == 4 ? 5 : pirq);
}
/* * The VIA pirq rules are nibble-based, like ALI, * but without the ugly irq number munging. * However, for 82C586, nibble map is different .
*/ staticint pirq_via586_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{ staticconstunsignedint pirqmap[5] = { 3, 2, 5, 1, 1 };
/* * ITE 8330G pirq rules are nibble-based * FIXME: pirqmap may be { 1, 0, 3, 2 }, * 2+3 are both mapped to irq 9 on my system
*/ staticint pirq_ite_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{ staticconstunsignedchar pirqmap[4] = { 1, 0, 2, 3 };
/* * OPTI: high four bits are nibble pointer.. * I wonder what the low bits do?
*/ staticint pirq_opti_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{ return read_config_nybble(router, 0xb8, pirq >> 4);
}
/* * Cyrix: nibble offset 0x5C * 0x5C bits 7:4 is INTB bits 3:0 is INTA * 0x5D bits 7:4 is INTD bits 3:0 is INTC
*/ staticint pirq_cyrix_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{ return read_config_nybble(router, 0x5C, (pirq-1)^1);
}
staticint pirq_cyrix_set(struct pci_dev *router, struct pci_dev *dev, int pirq, int irq)
{
write_config_nybble(router, 0x5C, (pirq-1)^1, irq); return 1;
}
/* * PIRQ routing for the SiS85C497 AT Bus Controller & Megacell (ATM) * ISA bridge used with the SiS 85C496/497 486 Green PC VESA/ISA/PCI * Chipset. * * There are four PCI INTx#-to-IRQ Link registers provided in the * SiS85C497 part of the peculiar combined 85C496/497 configuration * space decoded by the SiS85C496 PCI & CPU Memory Controller (PCM) * host bridge, at 0xc0/0xc1/0xc2/0xc3 respectively for the PCI INT * A/B/C/D lines. Bit 7 enables the respective link if set and bits * 3:0 select the 8259A IRQ line as follows: * * 0000 : Reserved * 0001 : Reserved * 0010 : Reserved * 0011 : IRQ3 * 0100 : IRQ4 * 0101 : IRQ5 * 0110 : IRQ6 * 0111 : IRQ7 * 1000 : Reserved * 1001 : IRQ9 * 1010 : IRQ10 * 1011 : IRQ11 * 1100 : IRQ12 * 1101 : Reserved * 1110 : IRQ14 * 1111 : IRQ15 * * We avoid using a reserved value for disabled links, hence the * choice of IRQ15 for that case. * * References: * * "486 Green PC VESA/ISA/PCI Chipset, SiS 85C496/497", Rev 3.0, * Silicon Integrated Systems Corp., July 1995
*/
/* * PIRQ routing for SiS 85C503 router used in several SiS chipsets. * We have to deal with the following issues here: * - vendors have different ideas about the meaning of link values * - some onboard devices (integrated in the chipset) have special * links and are thus routed differently (i.e. not via PCI INTA-INTD) * - different revision of the router have a different layout for * the routing registers, particularly for the onchip devices * * For all routing registers the common thing is we have one byte * per routeable link which is defined as: * bit 7 IRQ mapping enabled (0) or disabled (1) * bits [6:4] reserved (sometimes used for onchip devices) * bits [3:0] IRQ to map to * allowed: 3-7, 9-12, 14-15 * reserved: 0, 1, 2, 8, 13 * * The config-space registers located at 0x41/0x42/0x43/0x44 are * always used to route the normal PCI INT A/B/C/D respectively. * Apparently there are systems implementing PCI routing table using * link values 0x01-0x04 and others using 0x41-0x44 for PCI INTA..D. * We try our best to handle both link mappings. * * Currently (2003-05-21) it appears most SiS chipsets follow the * definition of routing registers from the SiS-5595 southbridge. * According to the SiS 5595 datasheets the revision id's of the * router (ISA-bridge) should be 0x01 or 0xb0. * * Furthermore we've also seen lspci dumps with revision 0x00 and 0xb1. * Looks like these are used in a number of SiS 5xx/6xx/7xx chipsets. * They seem to work with the current routing code. However there is * some concern because of the two USB-OHCI HCs (original SiS 5595 * had only one). YMMV. * * Onchip routing for router rev-id 0x01/0xb0 and probably 0x00/0xb1: * * 0x61: IDEIRQ: * bits [6:5] must be written 01 * bit 4 channel-select primary (0), secondary (1) * * 0x62: USBIRQ: * bit 6 OHCI function disabled (0), enabled (1) * * 0x6a: ACPI/SCI IRQ: bits 4-6 reserved * * 0x7e: Data Acq. Module IRQ - bits 4-6 reserved * * We support USBIRQ (in addition to INTA-INTD) and keep the * IDE, ACPI and DAQ routing untouched as set by the BIOS. * * Currently the only reported exception is the new SiS 65x chipset * which includes the SiS 69x southbridge. Here we have the 85C503 * router revision 0x04 and there are changes in the register layout * mostly related to the different USB HCs with USB 2.0 support. * * Onchip routing for router rev-id 0x04 (try-and-error observation) * * 0x60/0x61/0x62/0x63: 1xEHCI and 3xOHCI (companion) USB-HCs * bit 6-4 are probably unused, not like 5595
*/
/* * VLSI: nibble offset 0x74 - educated guess due to routing table and * config space of VLSI 82C534 PCI-bridge/router (1004:0102) * Tested on HP OmniBook 800 covering PIRQ 1, 2, 4, 8 for onboard * devices, PIRQ 3 for non-pci(!) soundchip and (untested) PIRQ 6 * for the busbridge to the docking station.
*/
/* * ServerWorks: PCI interrupts mapped to system IRQ lines through Index * and Redirect I/O registers (0x0c00 and 0x0c01). The Index register * format is (PCIIRQ## | 0x10), e.g.: PCIIRQ10=0x1a. The Redirect * register is a straight binary coding of desired PIC IRQ (low nibble). * * The 'link' value in the PIRQ table is already in the correct format * for the Index register. There are some special index values: * 0x00 for ACPI (SCI), 0x01 for USB, 0x02 for IDE0, 0x04 for IDE1, * and 0x03 for SMBus.
*/ staticint pirq_serverworks_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{
outb(pirq, 0xc00); return inb(0xc01) & 0xf;
}
staticint pirq_serverworks_set(struct pci_dev *router, struct pci_dev *dev, int pirq, int irq)
{
outb(pirq, 0xc00);
outb(irq, 0xc01); return 1;
}
/* Support for AMD756 PCI IRQ Routing * Jhon H. Caicedo <jhcaiced@osso.org.co> * Jun/21/2001 0.2.0 Release, fixed to use "nybble" functions... (jhcaiced) * Jun/19/2001 Alpha Release 0.1.0 (jhcaiced) * The AMD756 pirq rules are nibble-based * offset 0x56 0-3 PIRQA 4-7 PIRQB * offset 0x57 0-3 PIRQC 4-7 PIRQD
*/ staticint pirq_amd756_get(struct pci_dev *router, struct pci_dev *dev, int pirq)
{
u8 irq;
irq = 0; if (pirq <= 4)
irq = read_config_nybble(router, 0x56, pirq - 1);
dev_info(&dev->dev, "AMD756: dev [%04x:%04x], router PIRQ %d get IRQ %d\n",
dev->vendor, dev->device, pirq, irq); return irq;
}
staticint pirq_amd756_set(struct pci_dev *router, struct pci_dev *dev, int pirq, int irq)
{
dev_info(&dev->dev, "AMD756: dev [%04x:%04x], router PIRQ %d set IRQ %d\n",
dev->vendor, dev->device, pirq, irq); if (pirq <= 4)
write_config_nybble(router, 0x56, pirq - 1, irq); return 1;
}
/* 440GX has a proprietary PIRQ router -- don't use it */ if (pci_dev_present(pirq_440gx)) return 0;
switch (device) { case PCI_DEVICE_ID_INTEL_82375:
r->name = "PCEB/ESC";
r->get = pirq_esc_get;
r->set = pirq_esc_set; return 1; case PCI_DEVICE_ID_INTEL_82371FB_0: case PCI_DEVICE_ID_INTEL_82371SB_0: case PCI_DEVICE_ID_INTEL_82371AB_0: case PCI_DEVICE_ID_INTEL_82371MX: case PCI_DEVICE_ID_INTEL_82443MX_0: case PCI_DEVICE_ID_INTEL_82801AA_0: case PCI_DEVICE_ID_INTEL_82801AB_0: case PCI_DEVICE_ID_INTEL_82801BA_0: case PCI_DEVICE_ID_INTEL_82801BA_10: case PCI_DEVICE_ID_INTEL_82801CA_0: case PCI_DEVICE_ID_INTEL_82801CA_12: case PCI_DEVICE_ID_INTEL_82801DB_0: case PCI_DEVICE_ID_INTEL_82801E_0: case PCI_DEVICE_ID_INTEL_82801EB_0: case PCI_DEVICE_ID_INTEL_ESB_1: case PCI_DEVICE_ID_INTEL_ICH6_0: case PCI_DEVICE_ID_INTEL_ICH6_1: case PCI_DEVICE_ID_INTEL_ICH7_0: case PCI_DEVICE_ID_INTEL_ICH7_1: case PCI_DEVICE_ID_INTEL_ICH7_30: case PCI_DEVICE_ID_INTEL_ICH7_31: case PCI_DEVICE_ID_INTEL_TGP_LPC: case PCI_DEVICE_ID_INTEL_ESB2_0: case PCI_DEVICE_ID_INTEL_ICH8_0: case PCI_DEVICE_ID_INTEL_ICH8_1: case PCI_DEVICE_ID_INTEL_ICH8_2: case PCI_DEVICE_ID_INTEL_ICH8_3: case PCI_DEVICE_ID_INTEL_ICH8_4: case PCI_DEVICE_ID_INTEL_ICH9_0: case PCI_DEVICE_ID_INTEL_ICH9_1: case PCI_DEVICE_ID_INTEL_ICH9_2: case PCI_DEVICE_ID_INTEL_ICH9_3: case PCI_DEVICE_ID_INTEL_ICH9_4: case PCI_DEVICE_ID_INTEL_ICH9_5: case PCI_DEVICE_ID_INTEL_EP80579_0: case PCI_DEVICE_ID_INTEL_ICH10_0: case PCI_DEVICE_ID_INTEL_ICH10_1: case PCI_DEVICE_ID_INTEL_ICH10_2: case PCI_DEVICE_ID_INTEL_ICH10_3: case PCI_DEVICE_ID_INTEL_PATSBURG_LPC_0: case PCI_DEVICE_ID_INTEL_PATSBURG_LPC_1:
r->name = "PIIX/ICH";
r->get = pirq_piix_get;
r->set = pirq_piix_set; return 1; case PCI_DEVICE_ID_INTEL_82425:
r->name = "PSC/IB";
r->get = pirq_ib_get;
r->set = pirq_ib_set; return 1;
}
static __init int via_router_probe(struct irq_router *r, struct pci_dev *router, u16 device)
{ /* FIXME: We should move some of the quirk fixup stuff here */
/* * workarounds for some buggy BIOSes
*/ if (device == PCI_DEVICE_ID_VIA_82C586_0) { switch (router->device) { case PCI_DEVICE_ID_VIA_82C686: /* * Asus k7m bios wrongly reports 82C686A * as 586-compatible
*/
device = PCI_DEVICE_ID_VIA_82C686; break; case PCI_DEVICE_ID_VIA_8235: /** * Asus a7v-x bios wrongly reports 8235 * as 586-compatible
*/
device = PCI_DEVICE_ID_VIA_8235; break; case PCI_DEVICE_ID_VIA_8237: /** * Asus a7v600 bios wrongly reports 8237 * as 586-compatible
*/
device = PCI_DEVICE_ID_VIA_8237; break;
}
}
switch (device) { case PCI_DEVICE_ID_VIA_82C586_0:
r->name = "VIA";
r->get = pirq_via586_get;
r->set = pirq_via586_set; return 1; case PCI_DEVICE_ID_VIA_82C596: case PCI_DEVICE_ID_VIA_82C686: case PCI_DEVICE_ID_VIA_8231: case PCI_DEVICE_ID_VIA_8233A: case PCI_DEVICE_ID_VIA_8235: case PCI_DEVICE_ID_VIA_8237: /* FIXME: add new ones for 8233/5 */
r->name = "VIA";
r->get = pirq_via_get;
r->set = pirq_via_set; return 1;
} return 0;
}
DBG(KERN_DEBUG "PCI: Trying IRQ router for [%04x:%04x]\n",
dev->vendor, dev->device);
for (h = pirq_routers; h->vendor; h++) { /* First look for a router match */ if (rt->rtr_vendor == h->vendor &&
h->probe(r, dev, rt->rtr_device)) returntrue; /* Fall back to a device match */ if (dev->vendor == h->vendor &&
h->probe(r, dev, dev->device)) returntrue;
} returnfalse;
}
#ifdef CONFIG_PCI_BIOS if (!rt->signature) {
printk(KERN_INFO "PCI: Using BIOS for IRQ routing\n");
r->set = pirq_bios_set;
r->name = "BIOS"; return;
} #endif
/* Default unless a driver reloads it */
r->name = "default";
r->get = NULL;
r->set = NULL;
DBG(KERN_DEBUG "PCI: Attempting to find IRQ router for [%04x:%04x]\n",
rt->rtr_vendor, rt->rtr_device);
/* Use any vendor:device provided by the routing table or try all. */ if (rt->rtr_vendor) {
dev = pci_get_domain_bus_and_slot(0, rt->rtr_bus,
rt->rtr_devfn); if (dev && pirq_try_router(r, rt, dev))
pirq_router_dev = dev;
} else {
dev = NULL;
for_each_pci_dev(dev) { if (pirq_try_router(r, rt, dev)) {
pirq_router_dev = dev; break;
}
}
}
if (pirq_router_dev)
dev_info(&pirq_router_dev->dev, "%s IRQ router [%04x:%04x]\n",
pirq_router.name,
pirq_router_dev->vendor, pirq_router_dev->device); else
DBG(KERN_DEBUG "PCI: Interrupt router not found at " "%02x:%02x\n", rt->rtr_bus, rt->rtr_devfn);
/* The device remains referenced for the kernel lifetime */
}
/* * We're supposed to match on the PCI device only and not the function, * but some BIOSes build their tables with the PCI function included * for motherboard devices, so if a complete match is found, then give * it precedence over a slot match.
*/ staticstruct irq_info *pirq_get_dev_info(struct pci_dev *dev)
{ struct irq_routing_table *rt = pirq_table; int entries = (rt->size - sizeof(struct irq_routing_table)) / sizeof(struct irq_info); struct irq_info *slotinfo = NULL; struct irq_info *info;
for (info = rt->slots; entries--; info++) if (info->bus == dev->bus->number) { if (info->devfn == dev->devfn) return info; if (!slotinfo &&
PCI_SLOT(info->devfn) == PCI_SLOT(dev->devfn))
slotinfo = info;
} return slotinfo;
}
/* * Buses behind bridges are typically not listed in the PIRQ routing table. * Do the usual dance then and walk the tree of bridges up adjusting the * pin number accordingly on the way until the originating root bus device * has been reached and then use its routing information.
*/ staticstruct irq_info *pirq_get_info(struct pci_dev *dev, u8 *pin)
{ struct pci_dev *temp_dev = dev; struct irq_info *info;
u8 temp_pin = *pin;
u8 dpin = temp_pin;
info = pirq_get_dev_info(dev); while (!info && temp_dev->bus->parent) { struct pci_dev *bridge = temp_dev->bus->self;
temp_pin = pci_swizzle_interrupt_pin(temp_dev, temp_pin);
info = pirq_get_dev_info(bridge); if (info)
dev_warn(&dev->dev, "using bridge %s INT %c to get INT %c\n",
pci_name(bridge), 'A' + temp_pin - 1, 'A' + dpin - 1);
/* Update IRQ for all devices with the same pirq value */
for_each_pci_dev(dev2) {
pci_read_config_byte(dev2, PCI_INTERRUPT_PIN, &dpin); if (!dpin) continue;
pin = dpin;
info = pirq_get_info(dev2, &pin); if (!info) continue; if (info->irq[pin - 1].link == pirq) { /* * We refuse to override the dev->irq * information. Give a warning!
*/ if (dev2->irq && dev2->irq != irq && \
(!(pci_probe & PCI_USE_PIRQ_MASK) || \
((1 << dev2->irq) & mask))) { #ifndef CONFIG_PCI_MSI
dev_info(&dev2->dev, "IRQ routing conflict: " "have IRQ %d, want IRQ %d\n",
dev2->irq, irq); #endif continue;
}
dev2->irq = irq;
pirq_penalty[irq]++; if (dev != dev2)
dev_info(&dev->dev, "sharing IRQ %d with %s\n",
irq, pci_name(dev2));
}
} return 1;
}
DBG(KERN_DEBUG "PCI: IRQ fixup\n");
for_each_pci_dev(dev) { /* * If the BIOS has set an out of range IRQ number, just * ignore it. Also keep track of which IRQ's are * already in use.
*/ if (dev->irq >= 16) {
dev_dbg(&dev->dev, "ignoring bogus IRQ %d\n", dev->irq);
dev->irq = 0;
} /* * If the IRQ is already assigned to a PCI device, * ignore its ISA use penalty
*/ if (pirq_penalty[dev->irq] >= 100 &&
pirq_penalty[dev->irq] < 100000)
pirq_penalty[dev->irq] = 0;
pirq_penalty[dev->irq]++;
}
if (io_apic_assign_pci_irqs) return;
dev = NULL;
for_each_pci_dev(dev) {
pci_read_config_byte(dev, PCI_INTERRUPT_PIN, &pin); if (!pin) continue;
/* * Still no IRQ? Try to lookup one...
*/ if (!dev->irq)
pcibios_lookup_irq(dev, 0);
}
}
/* * Work around broken HP Pavilion Notebooks which assign USB to * IRQ 9 even though it is actually wired to IRQ 11
*/ staticint __init fix_broken_hp_bios_irq9(conststruct dmi_system_id *d)
{ if (!broken_hp_bios_irq9) {
broken_hp_bios_irq9 = 1;
printk(KERN_INFO "%s detected - fixing broken IRQ routing\n",
d->ident);
} return 0;
}
/* * Work around broken Acer TravelMate 360 Notebooks which assign * Cardbus to IRQ 11 even though it is actually wired to IRQ 10
*/ staticint __init fix_acer_tm360_irqrouting(conststruct dmi_system_id *d)
{ if (!acer_tm360_irqrouting) {
acer_tm360_irqrouting = 1;
printk(KERN_INFO "%s detected - fixing broken IRQ routing\n",
d->ident);
} return 0;
}
#ifdef CONFIG_PCI_BIOS if (!pirq_table && (pci_probe & PCI_BIOS_IRQ_SCAN)) {
pirq_table = pcibios_get_irq_routing_table();
rtable = pirq_table;
} #endif if (pirq_table) {
pirq_peer_trick();
pirq_find_router(&pirq_router); if (pirq_table->exclusive_irqs) { int i; for (i = 0; i < 16; i++) if (!(pirq_table->exclusive_irqs & (1 << i)))
pirq_penalty[i] += 100;
} /* * If we're using the I/O APIC, avoid using the PCI IRQ * routing table
*/ if (io_apic_assign_pci_irqs) {
kfree(rtable);
pirq_table = NULL;
}
}
x86_init.pci.fixup_irqs();
if (io_apic_assign_pci_irqs && pci_routeirq) { struct pci_dev *dev = NULL; /* * PCI IRQ routing is set up by pci_enable_device(), but we * also do it here in case there are still broken drivers that * don't use pci_enable_device().
*/
printk(KERN_INFO "PCI: Routing PCI interrupts for all devices because \"pci=routeirq\" specified\n");
for_each_pci_dev(dev)
pirq_enable_irq(dev);
}
}
staticvoid pirq_penalize_isa_irq(int irq, int active)
{ /* * If any ISAPnP device reports an IRQ in its list of possible * IRQ's, we try to avoid assigning it to PCI devices.
*/ if (irq < 16) { if (active)
pirq_penalty[irq] += 1000; else
pirq_penalty[irq] += 100;
}
}
void pcibios_penalize_isa_irq(int irq, int active)
{ #ifdef CONFIG_ACPI if (!acpi_noirq)
acpi_penalize_isa_irq(irq, active); else #endif
pirq_penalize_isa_irq(irq, active);
}
if (!io_apic_assign_pci_irqs && dev->irq) return 0;
if (io_apic_assign_pci_irqs) { #ifdef CONFIG_X86_IO_APIC struct pci_dev *temp_dev; int irq;
if (dev->irq_managed && dev->irq > 0) return 0;
irq = IO_APIC_get_PCI_irq_vector(dev->bus->number,
PCI_SLOT(dev->devfn), pin - 1); /* * Busses behind bridges are typically not listed in the MP-table. * In this case we have to look up the IRQ based on the parent bus, * parent slot, and pin number. The SMP code detects such bridged * busses itself so we should get into this branch reliably.
*/
temp_dev = dev; while (irq < 0 && dev->bus->parent) { /* go back to the bridge */ struct pci_dev *bridge = dev->bus->self;
/* * With IDE legacy devices the IRQ lookup failure is not * a problem..
*/ if (dev->class >> 8 == PCI_CLASS_STORAGE_IDE &&
!(dev->class & 0x5)) return 0;
dev_warn(&dev->dev, "can't find IRQ for PCI INT %c%s\n", 'A' + pin - 1, msg);
} return 0;
}
bool mp_should_keep_irq(struct device *dev)
{ if (dev->power.is_prepared) returntrue; #ifdef CONFIG_PM if (dev->power.runtime_status == RPM_SUSPENDING) returntrue; #endif
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.