2019-05-27 06:55:06 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* pci_irq.c - ACPI PCI Interrupt Routing ($Revision: 11 $)
|
|
|
|
*
|
|
|
|
* Copyright (C) 2001, 2002 Andy Grover <andrew.grover@intel.com>
|
|
|
|
* Copyright (C) 2001, 2002 Paul Diefenbaugh <paul.s.diefenbaugh@intel.com>
|
|
|
|
* Copyright (C) 2002 Dominik Brodowski <devel@brodo.de>
|
2008-12-09 04:31:42 +00:00
|
|
|
* (c) Copyright 2008 Hewlett-Packard Development Company, L.P.
|
|
|
|
* Bjorn Helgaas <bjorn.helgaas@hp.com>
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
|
|
|
|
2021-02-19 18:15:27 +00:00
|
|
|
#define pr_fmt(fmt) "ACPI: PCI: " fmt
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-03-11 20:45:15 +00:00
|
|
|
#include <linux/dmi.h>
|
2005-04-16 22:20:36 +00:00
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/spinlock.h>
|
|
|
|
#include <linux/pm.h>
|
|
|
|
#include <linux/pci.h>
|
|
|
|
#include <linux/acpi.h>
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 08:04:11 +00:00
|
|
|
#include <linux/slab.h>
|
x86/ACPI/PCI: Recognize that Interrupt Line 255 means "not connected"
Per the x86-specific footnote to PCI spec r3.0, sec 6.2.4, the value 255 in
the Interrupt Line register means "unknown" or "no connection."
Previously, when we couldn't derive an IRQ from the _PRT, we fell back to
using the value from Interrupt Line as an IRQ. It's questionable whether
we should do that at all, but the spec clearly suggests we shouldn't do it
for the value 255 on x86.
Calling request_irq() with IRQ 255 may succeed, but the driver won't
receive any interrupts. Or, if IRQ 255 is shared with another device, it
may succeed, and the driver's ISR will be called at random times when the
*other* device interrupts. Or it may fail if another device is using IRQ
255 with incompatible flags. What we *want* is for request_irq() to fail
predictably so the driver can fall back to polling.
On x86, assume 255 in the Interrupt Line means the INTx line is not
connected. In that case, set dev->irq to IRQ_NOTCONNECTED so request_irq()
will fail gracefully with -ENOTCONN.
We found this problem on a system where Secure Boot firmware assigned
Interrupt Line 255 to an i801_smbus device and another device was already
using MSI-X IRQ 255. This was in v3.10, where i801_probe() fails if
request_irq() fails:
i801_smbus 0000:00:1f.3: enabling device (0140 -> 0143)
i801_smbus 0000:00:1f.3: can't derive routing for PCI INT C
i801_smbus 0000:00:1f.3: PCI INT C: no GSI
genirq: Flags mismatch irq 255. 00000080 (i801_smbus) vs. 00000000 (megasa)
CPU: 0 PID: 2487 Comm: kworker/0:1 Not tainted 3.10.0-229.el7.x86_64 #1
Hardware name: FUJITSU PRIMEQUEST 2800E2/D3736, BIOS PRIMEQUEST 2000 Serie5
Call Trace:
dump_stack+0x19/0x1b
__setup_irq+0x54a/0x570
request_threaded_irq+0xcc/0x170
i801_probe+0x32f/0x508 [i2c_i801]
local_pci_probe+0x45/0xa0
i801_smbus 0000:00:1f.3: Failed to allocate irq 255: -16
i801_smbus: probe of 0000:00:1f.3 failed with error -16
After aeb8a3d16ae0 ("i2c: i801: Check if interrupts are disabled"),
i801_probe() will fall back to polling if request_irq() fails. But we
still need this patch because request_irq() may succeed or fail depending
on other devices in the system. If request_irq() fails, i801_smbus will
work by falling back to polling, but if it succeeds, i801_smbus won't work
because it expects interrupts that it may not receive.
Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2016-02-15 04:52:01 +00:00
|
|
|
#include <linux/interrupt.h>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-12-09 04:30:31 +00:00
|
|
|
struct acpi_prt_entry {
|
|
|
|
struct acpi_pci_id id;
|
|
|
|
u8 pin;
|
2008-12-09 04:31:27 +00:00
|
|
|
acpi_handle link;
|
|
|
|
u32 index; /* GSI, or link _CRS index */
|
2008-12-09 04:30:31 +00:00
|
|
|
};
|
|
|
|
|
2008-12-09 04:30:36 +00:00
|
|
|
static inline char pin_name(int pin)
|
|
|
|
{
|
2008-12-09 04:30:41 +00:00
|
|
|
return 'A' + pin - 1;
|
2008-12-09 04:30:36 +00:00
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/* --------------------------------------------------------------------------
|
|
|
|
PCI IRQ Routing Table (PRT) Support
|
|
|
|
-------------------------------------------------------------------------- */
|
|
|
|
|
2008-03-11 20:45:15 +00:00
|
|
|
/* http://bugzilla.kernel.org/show_bug.cgi?id=4773 */
|
2009-03-12 11:58:25 +00:00
|
|
|
static const struct dmi_system_id medion_md9580[] = {
|
2008-03-11 20:45:15 +00:00
|
|
|
{
|
|
|
|
.ident = "Medion MD9580-F laptop",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "MEDIONNB"),
|
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "A555"),
|
|
|
|
},
|
|
|
|
},
|
|
|
|
{ }
|
|
|
|
};
|
|
|
|
|
|
|
|
/* http://bugzilla.kernel.org/show_bug.cgi?id=5044 */
|
2009-03-12 11:58:25 +00:00
|
|
|
static const struct dmi_system_id dell_optiplex[] = {
|
2008-03-11 20:45:15 +00:00
|
|
|
{
|
|
|
|
.ident = "Dell Optiplex GX1",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "Dell Computer Corporation"),
|
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "OptiPlex GX1 600S+"),
|
|
|
|
},
|
|
|
|
},
|
|
|
|
{ }
|
|
|
|
};
|
|
|
|
|
|
|
|
/* http://bugzilla.kernel.org/show_bug.cgi?id=10138 */
|
2009-03-12 11:58:25 +00:00
|
|
|
static const struct dmi_system_id hp_t5710[] = {
|
2008-03-11 20:45:15 +00:00
|
|
|
{
|
|
|
|
.ident = "HP t5710",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"),
|
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "hp t5000 series"),
|
|
|
|
DMI_MATCH(DMI_BOARD_NAME, "098Ch"),
|
|
|
|
},
|
|
|
|
},
|
|
|
|
{ }
|
|
|
|
};
|
|
|
|
|
|
|
|
struct prt_quirk {
|
2009-03-12 11:58:25 +00:00
|
|
|
const struct dmi_system_id *system;
|
2008-03-11 20:45:15 +00:00
|
|
|
unsigned int segment;
|
|
|
|
unsigned int bus;
|
|
|
|
unsigned int device;
|
|
|
|
unsigned char pin;
|
2009-03-12 11:58:25 +00:00
|
|
|
const char *source; /* according to BIOS */
|
|
|
|
const char *actual_source;
|
2008-03-11 20:45:15 +00:00
|
|
|
};
|
|
|
|
|
2008-12-09 04:30:46 +00:00
|
|
|
#define PCI_INTX_PIN(c) (c - 'A' + 1)
|
|
|
|
|
2008-03-11 20:45:15 +00:00
|
|
|
/*
|
|
|
|
* These systems have incorrect _PRT entries. The BIOS claims the PCI
|
|
|
|
* interrupt at the listed segment/bus/device/pin is connected to the first
|
|
|
|
* link device, but it is actually connected to the second.
|
|
|
|
*/
|
2009-03-12 11:58:25 +00:00
|
|
|
static const struct prt_quirk prt_quirks[] = {
|
2008-12-09 04:30:46 +00:00
|
|
|
{ medion_md9580, 0, 0, 9, PCI_INTX_PIN('A'),
|
2008-03-25 17:21:11 +00:00
|
|
|
"\\_SB_.PCI0.ISA_.LNKA",
|
|
|
|
"\\_SB_.PCI0.ISA_.LNKB"},
|
2008-12-09 04:30:46 +00:00
|
|
|
{ dell_optiplex, 0, 0, 0xd, PCI_INTX_PIN('A'),
|
2008-03-11 20:45:15 +00:00
|
|
|
"\\_SB_.LNKB",
|
|
|
|
"\\_SB_.LNKA"},
|
2008-12-09 04:30:46 +00:00
|
|
|
{ hp_t5710, 0, 0, 1, PCI_INTX_PIN('A'),
|
2008-03-11 20:45:15 +00:00
|
|
|
"\\_SB_.PCI0.LNK1",
|
|
|
|
"\\_SB_.PCI0.LNK3"},
|
|
|
|
};
|
|
|
|
|
2008-12-09 04:31:37 +00:00
|
|
|
static void do_prt_fixups(struct acpi_prt_entry *entry,
|
|
|
|
struct acpi_pci_routing_table *prt)
|
2008-03-11 20:45:15 +00:00
|
|
|
{
|
|
|
|
int i;
|
2009-03-12 11:58:25 +00:00
|
|
|
const struct prt_quirk *quirk;
|
2008-03-11 20:45:15 +00:00
|
|
|
|
|
|
|
for (i = 0; i < ARRAY_SIZE(prt_quirks); i++) {
|
|
|
|
quirk = &prt_quirks[i];
|
|
|
|
|
|
|
|
/* All current quirks involve link devices, not GSIs */
|
|
|
|
if (dmi_check_system(quirk->system) &&
|
|
|
|
entry->id.segment == quirk->segment &&
|
|
|
|
entry->id.bus == quirk->bus &&
|
|
|
|
entry->id.device == quirk->device &&
|
2008-12-09 04:30:46 +00:00
|
|
|
entry->pin == quirk->pin &&
|
2008-03-11 20:45:15 +00:00
|
|
|
!strcmp(prt->source, quirk->source) &&
|
|
|
|
strlen(prt->source) >= strlen(quirk->actual_source)) {
|
2021-02-19 18:15:27 +00:00
|
|
|
pr_warn("Firmware reports "
|
2008-06-27 14:45:39 +00:00
|
|
|
"%04x:%02x:%02x PCI INT %c connected to %s; "
|
2008-03-11 20:45:15 +00:00
|
|
|
"changing to %s\n",
|
|
|
|
entry->id.segment, entry->id.bus,
|
2008-12-09 04:30:36 +00:00
|
|
|
entry->id.device, pin_name(entry->pin),
|
2008-03-11 20:45:15 +00:00
|
|
|
prt->source, quirk->actual_source);
|
|
|
|
strcpy(prt->source, quirk->actual_source);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
static int acpi_pci_irq_check_entry(acpi_handle handle, struct pci_dev *dev,
|
|
|
|
int pin, struct acpi_pci_routing_table *prt,
|
|
|
|
struct acpi_prt_entry **entry_ptr)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2013-02-16 18:58:34 +00:00
|
|
|
int segment = pci_domain_nr(dev->bus);
|
|
|
|
int bus = dev->bus->number;
|
2015-05-26 21:11:51 +00:00
|
|
|
int device = pci_ari_enabled(dev->bus) ? 0 : PCI_SLOT(dev->devfn);
|
2008-12-09 04:31:21 +00:00
|
|
|
struct acpi_prt_entry *entry;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
if (((prt->address >> 16) & 0xffff) != device ||
|
|
|
|
prt->pin + 1 != pin)
|
|
|
|
return -ENODEV;
|
|
|
|
|
2006-12-19 20:56:11 +00:00
|
|
|
entry = kzalloc(sizeof(struct acpi_prt_entry), GFP_KERNEL);
|
2005-04-16 22:20:36 +00:00
|
|
|
if (!entry)
|
2006-06-27 04:41:40 +00:00
|
|
|
return -ENOMEM;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-12-09 04:30:41 +00:00
|
|
|
/*
|
|
|
|
* Note that the _PRT uses 0=INTA, 1=INTB, etc, while PCI uses
|
|
|
|
* 1=INTA, 2=INTB. We use the PCI encoding throughout, so convert
|
|
|
|
* it here.
|
|
|
|
*/
|
2012-10-30 06:24:06 +00:00
|
|
|
entry->id.segment = segment;
|
|
|
|
entry->id.bus = bus;
|
2005-04-16 22:20:36 +00:00
|
|
|
entry->id.device = (prt->address >> 16) & 0xFFFF;
|
2008-12-09 04:30:41 +00:00
|
|
|
entry->pin = prt->pin + 1;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-03-11 20:45:15 +00:00
|
|
|
do_prt_fixups(entry, prt);
|
|
|
|
|
2008-12-09 04:31:27 +00:00
|
|
|
entry->index = prt->source_index;
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* Type 1: Dynamic
|
|
|
|
* ---------------
|
|
|
|
* The 'source' field specifies the PCI interrupt link device used to
|
|
|
|
* configure the IRQ assigned to this slot|dev|pin. The 'source_index'
|
|
|
|
* indicates which resource descriptor in the resource template (of
|
|
|
|
* the link device) this interrupt is allocated from.
|
2020-11-05 02:06:00 +00:00
|
|
|
*
|
2005-04-16 22:20:36 +00:00
|
|
|
* NOTE: Don't query the Link Device for IRQ information at this time
|
|
|
|
* because Link Device enumeration may not have occurred yet
|
|
|
|
* (e.g. exists somewhere 'below' this _PRT entry in the ACPI
|
|
|
|
* namespace).
|
|
|
|
*/
|
2008-12-09 04:31:27 +00:00
|
|
|
if (prt->source[0])
|
|
|
|
acpi_get_handle(handle, prt->source, &entry->link);
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* Type 2: Static
|
|
|
|
* --------------
|
|
|
|
* The 'source' field is NULL, and the 'source_index' field specifies
|
|
|
|
* the IRQ value, which is hardwired to specific interrupt inputs on
|
|
|
|
* the interrupt controller.
|
|
|
|
*/
|
2021-02-19 18:15:27 +00:00
|
|
|
pr_debug("%04x:%02x:%02x[%c] -> %s[%d]\n",
|
|
|
|
entry->id.segment, entry->id.bus, entry->id.device,
|
|
|
|
pin_name(entry->pin), prt->source, entry->index);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
*entry_ptr = entry;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-06-27 04:41:40 +00:00
|
|
|
return 0;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
static int acpi_pci_irq_find_prt_entry(struct pci_dev *dev,
|
|
|
|
int pin, struct acpi_prt_entry **entry_ptr)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2008-12-09 04:30:15 +00:00
|
|
|
acpi_status status;
|
|
|
|
struct acpi_buffer buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
|
|
|
struct acpi_pci_routing_table *entry;
|
2013-02-16 18:58:34 +00:00
|
|
|
acpi_handle handle = NULL;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
if (dev->bus->bridge)
|
|
|
|
handle = ACPI_HANDLE(dev->bus->bridge);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
if (!handle)
|
|
|
|
return -ENODEV;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
/* 'handle' is the _PRT's parent (root bridge or PCI-PCI bridge) */
|
2005-04-16 22:20:36 +00:00
|
|
|
status = acpi_get_irq_routing_table(handle, &buffer);
|
|
|
|
if (ACPI_FAILURE(status)) {
|
|
|
|
kfree(buffer.pointer);
|
2006-06-27 04:41:40 +00:00
|
|
|
return -ENODEV;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2008-12-09 04:30:15 +00:00
|
|
|
entry = buffer.pointer;
|
2005-04-16 22:20:36 +00:00
|
|
|
while (entry && (entry->length > 0)) {
|
2013-02-16 18:58:34 +00:00
|
|
|
if (!acpi_pci_irq_check_entry(handle, dev, pin,
|
|
|
|
entry, entry_ptr))
|
|
|
|
break;
|
2005-04-16 22:20:36 +00:00
|
|
|
entry = (struct acpi_pci_routing_table *)
|
2005-08-05 04:44:28 +00:00
|
|
|
((unsigned long)entry + entry->length);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2008-12-09 04:30:15 +00:00
|
|
|
kfree(buffer.pointer);
|
2006-06-27 04:41:40 +00:00
|
|
|
return 0;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* --------------------------------------------------------------------------
|
|
|
|
PCI Interrupt Routing Support
|
|
|
|
-------------------------------------------------------------------------- */
|
2011-07-15 12:52:30 +00:00
|
|
|
#ifdef CONFIG_X86_IO_APIC
|
|
|
|
extern int noioapicquirk;
|
|
|
|
extern int noioapicreroute;
|
|
|
|
|
|
|
|
static int bridge_has_boot_interrupt_variant(struct pci_bus *bus)
|
|
|
|
{
|
|
|
|
struct pci_bus *bus_it;
|
|
|
|
|
|
|
|
for (bus_it = bus ; bus_it ; bus_it = bus_it->parent) {
|
|
|
|
if (!bus_it->self)
|
|
|
|
return 0;
|
|
|
|
if (bus_it->self->irq_reroute_variant)
|
|
|
|
return bus_it->self->irq_reroute_variant;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Some chipsets (e.g. Intel 6700PXH) generate a legacy INTx when the IRQ
|
|
|
|
* entry in the chipset's IO-APIC is masked (as, e.g. the RT kernel does
|
|
|
|
* during interrupt handling). When this INTx generation cannot be disabled,
|
|
|
|
* we reroute these interrupts to their legacy equivalent to get rid of
|
|
|
|
* spurious interrupts.
|
|
|
|
*/
|
|
|
|
static int acpi_reroute_boot_interrupt(struct pci_dev *dev,
|
|
|
|
struct acpi_prt_entry *entry)
|
|
|
|
{
|
|
|
|
if (noioapicquirk || noioapicreroute) {
|
|
|
|
return 0;
|
|
|
|
} else {
|
|
|
|
switch (bridge_has_boot_interrupt_variant(dev->bus)) {
|
|
|
|
case 0:
|
|
|
|
/* no rerouting necessary */
|
|
|
|
return 0;
|
|
|
|
case INTEL_IRQ_REROUTE_VARIANT:
|
|
|
|
/*
|
|
|
|
* Remap according to INTx routing table in 6700PXH
|
|
|
|
* specs, intel order number 302628-002, section
|
|
|
|
* 2.15.2. Other chipsets (80332, ...) have the same
|
|
|
|
* mapping and are handled here as well.
|
|
|
|
*/
|
|
|
|
dev_info(&dev->dev, "PCI IRQ %d -> rerouted to legacy "
|
|
|
|
"IRQ %d\n", entry->index,
|
|
|
|
(entry->index % 4) + 16);
|
|
|
|
entry->index = (entry->index % 4) + 16;
|
|
|
|
return 1;
|
|
|
|
default:
|
|
|
|
dev_warn(&dev->dev, "Cannot reroute IRQ %d to legacy "
|
|
|
|
"IRQ: unknown mapping\n", entry->index);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
#endif /* CONFIG_X86_IO_APIC */
|
|
|
|
|
2008-12-09 04:31:37 +00:00
|
|
|
static struct acpi_prt_entry *acpi_pci_irq_lookup(struct pci_dev *dev, int pin)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2013-02-16 18:58:34 +00:00
|
|
|
struct acpi_prt_entry *entry = NULL;
|
2008-12-09 04:31:16 +00:00
|
|
|
struct pci_dev *bridge;
|
|
|
|
u8 bridge_pin, orig_pin = pin;
|
2013-02-16 18:58:34 +00:00
|
|
|
int ret;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
ret = acpi_pci_irq_find_prt_entry(dev, pin, &entry);
|
|
|
|
if (!ret && entry) {
|
2011-07-15 12:52:30 +00:00
|
|
|
#ifdef CONFIG_X86_IO_APIC
|
|
|
|
acpi_reroute_boot_interrupt(dev, entry);
|
|
|
|
#endif /* CONFIG_X86_IO_APIC */
|
2021-02-19 18:15:27 +00:00
|
|
|
dev_dbg(&dev->dev, "Found [%c] _PRT entry\n", pin_name(pin));
|
2008-12-09 04:31:06 +00:00
|
|
|
return entry;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
2005-08-05 04:44:28 +00:00
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
/*
|
2005-04-16 22:20:36 +00:00
|
|
|
* Attempt to derive an IRQ for this device from a parent bridge's
|
|
|
|
* PCI interrupt routing entry (eg. yenta bridge and add-in card bridge).
|
|
|
|
*/
|
2008-12-09 04:31:11 +00:00
|
|
|
bridge = dev->bus->self;
|
|
|
|
while (bridge) {
|
2009-02-17 20:49:10 +00:00
|
|
|
pin = pci_swizzle_interrupt_pin(dev, pin);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
if ((bridge->class >> 8) == PCI_CLASS_BRIDGE_CARDBUS) {
|
|
|
|
/* PC card has the same IRQ as its cardbridge */
|
2005-11-03 00:24:35 +00:00
|
|
|
bridge_pin = bridge->pin;
|
2005-04-16 22:20:36 +00:00
|
|
|
if (!bridge_pin) {
|
2021-02-19 18:15:27 +00:00
|
|
|
dev_dbg(&bridge->dev, "No interrupt pin configured\n");
|
2008-12-09 04:31:01 +00:00
|
|
|
return NULL;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
pin = bridge_pin;
|
|
|
|
}
|
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
ret = acpi_pci_irq_find_prt_entry(bridge, pin, &entry);
|
|
|
|
if (!ret && entry) {
|
2021-02-19 18:15:27 +00:00
|
|
|
dev_dbg(&dev->dev, "Derived GSI INT %c from %s\n",
|
|
|
|
pin_name(orig_pin), pci_name(bridge));
|
2008-12-09 04:31:06 +00:00
|
|
|
return entry;
|
|
|
|
}
|
2008-12-09 04:31:11 +00:00
|
|
|
|
|
|
|
dev = bridge;
|
|
|
|
bridge = dev->bus->self;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2008-12-09 04:31:06 +00:00
|
|
|
dev_warn(&dev->dev, "can't derive routing for PCI INT %c\n",
|
|
|
|
pin_name(orig_pin));
|
|
|
|
return NULL;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2014-02-20 13:27:46 +00:00
|
|
|
#if IS_ENABLED(CONFIG_ISA) || IS_ENABLED(CONFIG_EISA)
|
|
|
|
static int acpi_isa_register_gsi(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
u32 dev_gsi;
|
|
|
|
|
|
|
|
/* Interrupt Line values above 0xF are forbidden */
|
|
|
|
if (dev->irq > 0 && (dev->irq <= 0xF) &&
|
2015-09-17 06:02:45 +00:00
|
|
|
acpi_isa_irq_available(dev->irq) &&
|
2014-02-20 13:27:46 +00:00
|
|
|
(acpi_isa_irq_to_gsi(dev->irq, &dev_gsi) == 0)) {
|
|
|
|
dev_warn(&dev->dev, "PCI INT %c: no GSI - using ISA IRQ %d\n",
|
|
|
|
pin_name(dev->pin), dev->irq);
|
|
|
|
acpi_register_gsi(&dev->dev, dev_gsi,
|
|
|
|
ACPI_LEVEL_SENSITIVE,
|
|
|
|
ACPI_ACTIVE_LOW);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
#else
|
|
|
|
static inline int acpi_isa_register_gsi(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
x86/ACPI/PCI: Recognize that Interrupt Line 255 means "not connected"
Per the x86-specific footnote to PCI spec r3.0, sec 6.2.4, the value 255 in
the Interrupt Line register means "unknown" or "no connection."
Previously, when we couldn't derive an IRQ from the _PRT, we fell back to
using the value from Interrupt Line as an IRQ. It's questionable whether
we should do that at all, but the spec clearly suggests we shouldn't do it
for the value 255 on x86.
Calling request_irq() with IRQ 255 may succeed, but the driver won't
receive any interrupts. Or, if IRQ 255 is shared with another device, it
may succeed, and the driver's ISR will be called at random times when the
*other* device interrupts. Or it may fail if another device is using IRQ
255 with incompatible flags. What we *want* is for request_irq() to fail
predictably so the driver can fall back to polling.
On x86, assume 255 in the Interrupt Line means the INTx line is not
connected. In that case, set dev->irq to IRQ_NOTCONNECTED so request_irq()
will fail gracefully with -ENOTCONN.
We found this problem on a system where Secure Boot firmware assigned
Interrupt Line 255 to an i801_smbus device and another device was already
using MSI-X IRQ 255. This was in v3.10, where i801_probe() fails if
request_irq() fails:
i801_smbus 0000:00:1f.3: enabling device (0140 -> 0143)
i801_smbus 0000:00:1f.3: can't derive routing for PCI INT C
i801_smbus 0000:00:1f.3: PCI INT C: no GSI
genirq: Flags mismatch irq 255. 00000080 (i801_smbus) vs. 00000000 (megasa)
CPU: 0 PID: 2487 Comm: kworker/0:1 Not tainted 3.10.0-229.el7.x86_64 #1
Hardware name: FUJITSU PRIMEQUEST 2800E2/D3736, BIOS PRIMEQUEST 2000 Serie5
Call Trace:
dump_stack+0x19/0x1b
__setup_irq+0x54a/0x570
request_threaded_irq+0xcc/0x170
i801_probe+0x32f/0x508 [i2c_i801]
local_pci_probe+0x45/0xa0
i801_smbus 0000:00:1f.3: Failed to allocate irq 255: -16
i801_smbus: probe of 0000:00:1f.3 failed with error -16
After aeb8a3d16ae0 ("i2c: i801: Check if interrupts are disabled"),
i801_probe() will fall back to polling if request_irq() fails. But we
still need this patch because request_irq() may succeed or fail depending
on other devices in the system. If request_irq() fails, i801_smbus will
work by falling back to polling, but if it succeeds, i801_smbus won't work
because it expects interrupts that it may not receive.
Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2016-02-15 04:52:01 +00:00
|
|
|
static inline bool acpi_pci_irq_valid(struct pci_dev *dev, u8 pin)
|
|
|
|
{
|
|
|
|
#ifdef CONFIG_X86
|
|
|
|
/*
|
|
|
|
* On x86 irq line 0xff means "unknown" or "no connection"
|
|
|
|
* (PCI 3.0, Section 6.2.4, footnote on page 223).
|
|
|
|
*/
|
|
|
|
if (dev->irq == 0xff) {
|
|
|
|
dev->irq = IRQ_NOTCONNECTED;
|
|
|
|
dev_warn(&dev->dev, "PCI INT %c: not connected\n",
|
|
|
|
pin_name(pin));
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2005-08-05 04:44:28 +00:00
|
|
|
int acpi_pci_irq_enable(struct pci_dev *dev)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2008-12-09 04:31:01 +00:00
|
|
|
struct acpi_prt_entry *entry;
|
2008-12-09 04:31:37 +00:00
|
|
|
int gsi;
|
|
|
|
u8 pin;
|
[ACPI] ACPICA 20050930
Completed a major overhaul of the Resource Manager code -
specifically, optimizations in the area of the AML/internal
resource conversion code. The code has been optimized to
simplify and eliminate duplicated code, CPU stack use has
been decreased by optimizing function parameters and local
variables, and naming conventions across the manager have
been standardized for clarity and ease of maintenance (this
includes function, parameter, variable, and struct/typedef
names.)
All Resource Manager dispatch and information tables have
been moved to a single location for clarity and ease of
maintenance. One new file was created, named "rsinfo.c".
The ACPI return macros (return_ACPI_STATUS, etc.) have
been modified to guarantee that the argument is
not evaluated twice, making them less prone to macro
side-effects. However, since there exists the possibility
of additional stack use if a particular compiler cannot
optimize them (such as in the debug generation case),
the original macros are optionally available. Note that
some invocations of the return_VALUE macro may now cause
size mismatch warnings; the return_UINT8 and return_UINT32
macros are provided to eliminate these. (From Randy Dunlap)
Implemented a new mechanism to enable debug tracing for
individual control methods. A new external interface,
acpi_debug_trace(), is provided to enable this mechanism. The
intent is to allow the host OS to easily enable and disable
tracing for problematic control methods. This interface
can be easily exposed to a user or debugger interface if
desired. See the file psxface.c for details.
acpi_ut_callocate() will now return a valid pointer if a
length of zero is specified - a length of one is used
and a warning is issued. This matches the behavior of
acpi_ut_allocate().
Signed-off-by: Bob Moore <robert.moore@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2005-09-30 23:03:00 +00:00
|
|
|
int triggering = ACPI_LEVEL_SENSITIVE;
|
ACPI / PCI: fix GIC irq model default PCI IRQ polarity
On ACPI ARM based systems the GIC interrupt controller
and corresponding interrupt model permit only the high
polarity for level interrupts.
ACPI firmware describes PCI legacy IRQs through entries
in the _PRT objects. Entries in the _PRT can be of two types:
- Static: not configurable, trigger/polarity default to level-low,
_PRT entry defines the global GSI interrupt number
- Configurable: _PRT interrupt entry contains a reference to the
corresponding PCI interrupt link device (that in turn provides the
interrupt descriptor through its _CRS/_PRS methods)
Configurable IRQ entries are not currently allowed by the ACPI
specification on ARM since they can only be used for interrupt pins that
are routable, as per ACPI specifications (version 6.1, 6.2.13):
"[...] There are two ways that _PRT can be used. Typically, the
interrupt input that a given PCI interrupt is on is configurable. For
example, a given PCI interrupt might be configured for either IRQ 10 or
11 on an 8259 interrupt controller. In this model, each interrupt is
represented in the ACPI namespace as a PCI Interrupt Link Device. [...]"
ARM platforms GIC configurations do not allow dynamic IRQ routing,
since routing is statically laid out at synthesis time; therefore PCI
interrupt links cannot be used for PCI legacy IRQ descriptions in the
_PRT on ARM systems.
On the other hand, current core ACPI code handling PCI legacy IRQs
consider IRQ trigger/polarity for static _PRT entries as level-low.
On ARM systems with a GIC interrupt controller and corresponding
ACPI interrupt model this does not work in that GIC interrupt
controller is only capable of handling level interrupts whose
polarity is high (for PCI legacy IRQs - that are level-low by
specification - this means that the legacy IRQs are inverted before
reaching the interrupt controller pin), resulting in IRQ allocation
failures such as:
genirq: Setting trigger mode 8 for irq 18 failed (gic_set_type+0x0/0x48)
Change the default polarity for PCI legacy IRQs to high on systems
booting wth ACPI on platforms with a GIC interrupt controller model,
fixing the discrepancy between specification and HW behaviour.
Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Tested-by: Duc Dang <dhdang@apm.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2016-09-05 14:12:38 +00:00
|
|
|
/*
|
ACPI / PCI: fix LPIC IRQ model default PCI IRQ polarity
On LoongArch based systems, the PCI devices (e.g. SATA controllers and
PCI-to-PCI bridge controllers) in Loongson chipsets output high-level
interrupt signal to the interrupt controller they are connected (see
Loongson 7A1000 Bridge User Manual v2.00, sec 5.3, "For the bridge chip,
AC97 DMA interrupts are edge triggered, gpio interrupts can be configured
to be level triggered or edge triggered as needed, and the rest of the
interrupts are level triggered and active high."), while the IRQs are
active low from the perspective of PCI (see Conventional PCI spec r3.0,
sec 2.2.6, "Interrupts on PCI are optional and defined as level sensitive,
asserted low."), which means that the interrupt output of PCI devices plugged
into PCI-to-PCI bridges of Loongson chipset will be also converted to high-level.
So high level triggered type is required to be passed to acpi_register_gsi()
when creating mappings for PCI devices.
Signed-off-by: Jianmin Lv <lvjianmin@loongson.cn>
Reviewed-by: Huacai Chen <chenhuacai@loongson.cn>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20221022075955.11726-2-lvjianmin@loongson.cn
2022-10-22 07:59:52 +00:00
|
|
|
* On ARM systems with the GIC interrupt model, or LoongArch
|
|
|
|
* systems with the LPIC interrupt model, level interrupts
|
ACPI / PCI: fix GIC irq model default PCI IRQ polarity
On ACPI ARM based systems the GIC interrupt controller
and corresponding interrupt model permit only the high
polarity for level interrupts.
ACPI firmware describes PCI legacy IRQs through entries
in the _PRT objects. Entries in the _PRT can be of two types:
- Static: not configurable, trigger/polarity default to level-low,
_PRT entry defines the global GSI interrupt number
- Configurable: _PRT interrupt entry contains a reference to the
corresponding PCI interrupt link device (that in turn provides the
interrupt descriptor through its _CRS/_PRS methods)
Configurable IRQ entries are not currently allowed by the ACPI
specification on ARM since they can only be used for interrupt pins that
are routable, as per ACPI specifications (version 6.1, 6.2.13):
"[...] There are two ways that _PRT can be used. Typically, the
interrupt input that a given PCI interrupt is on is configurable. For
example, a given PCI interrupt might be configured for either IRQ 10 or
11 on an 8259 interrupt controller. In this model, each interrupt is
represented in the ACPI namespace as a PCI Interrupt Link Device. [...]"
ARM platforms GIC configurations do not allow dynamic IRQ routing,
since routing is statically laid out at synthesis time; therefore PCI
interrupt links cannot be used for PCI legacy IRQ descriptions in the
_PRT on ARM systems.
On the other hand, current core ACPI code handling PCI legacy IRQs
consider IRQ trigger/polarity for static _PRT entries as level-low.
On ARM systems with a GIC interrupt controller and corresponding
ACPI interrupt model this does not work in that GIC interrupt
controller is only capable of handling level interrupts whose
polarity is high (for PCI legacy IRQs - that are level-low by
specification - this means that the legacy IRQs are inverted before
reaching the interrupt controller pin), resulting in IRQ allocation
failures such as:
genirq: Setting trigger mode 8 for irq 18 failed (gic_set_type+0x0/0x48)
Change the default polarity for PCI legacy IRQs to high on systems
booting wth ACPI on platforms with a GIC interrupt controller model,
fixing the discrepancy between specification and HW behaviour.
Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Tested-by: Duc Dang <dhdang@apm.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2016-09-05 14:12:38 +00:00
|
|
|
* are always polarity high by specification; PCI legacy
|
|
|
|
* IRQs lines are inverted before reaching the interrupt
|
|
|
|
* controller and must therefore be considered active high
|
|
|
|
* as default.
|
|
|
|
*/
|
ACPI / PCI: fix LPIC IRQ model default PCI IRQ polarity
On LoongArch based systems, the PCI devices (e.g. SATA controllers and
PCI-to-PCI bridge controllers) in Loongson chipsets output high-level
interrupt signal to the interrupt controller they are connected (see
Loongson 7A1000 Bridge User Manual v2.00, sec 5.3, "For the bridge chip,
AC97 DMA interrupts are edge triggered, gpio interrupts can be configured
to be level triggered or edge triggered as needed, and the rest of the
interrupts are level triggered and active high."), while the IRQs are
active low from the perspective of PCI (see Conventional PCI spec r3.0,
sec 2.2.6, "Interrupts on PCI are optional and defined as level sensitive,
asserted low."), which means that the interrupt output of PCI devices plugged
into PCI-to-PCI bridges of Loongson chipset will be also converted to high-level.
So high level triggered type is required to be passed to acpi_register_gsi()
when creating mappings for PCI devices.
Signed-off-by: Jianmin Lv <lvjianmin@loongson.cn>
Reviewed-by: Huacai Chen <chenhuacai@loongson.cn>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20221022075955.11726-2-lvjianmin@loongson.cn
2022-10-22 07:59:52 +00:00
|
|
|
int polarity = acpi_irq_model == ACPI_IRQ_MODEL_GIC ||
|
|
|
|
acpi_irq_model == ACPI_IRQ_MODEL_LPIC ?
|
ACPI / PCI: fix GIC irq model default PCI IRQ polarity
On ACPI ARM based systems the GIC interrupt controller
and corresponding interrupt model permit only the high
polarity for level interrupts.
ACPI firmware describes PCI legacy IRQs through entries
in the _PRT objects. Entries in the _PRT can be of two types:
- Static: not configurable, trigger/polarity default to level-low,
_PRT entry defines the global GSI interrupt number
- Configurable: _PRT interrupt entry contains a reference to the
corresponding PCI interrupt link device (that in turn provides the
interrupt descriptor through its _CRS/_PRS methods)
Configurable IRQ entries are not currently allowed by the ACPI
specification on ARM since they can only be used for interrupt pins that
are routable, as per ACPI specifications (version 6.1, 6.2.13):
"[...] There are two ways that _PRT can be used. Typically, the
interrupt input that a given PCI interrupt is on is configurable. For
example, a given PCI interrupt might be configured for either IRQ 10 or
11 on an 8259 interrupt controller. In this model, each interrupt is
represented in the ACPI namespace as a PCI Interrupt Link Device. [...]"
ARM platforms GIC configurations do not allow dynamic IRQ routing,
since routing is statically laid out at synthesis time; therefore PCI
interrupt links cannot be used for PCI legacy IRQ descriptions in the
_PRT on ARM systems.
On the other hand, current core ACPI code handling PCI legacy IRQs
consider IRQ trigger/polarity for static _PRT entries as level-low.
On ARM systems with a GIC interrupt controller and corresponding
ACPI interrupt model this does not work in that GIC interrupt
controller is only capable of handling level interrupts whose
polarity is high (for PCI legacy IRQs - that are level-low by
specification - this means that the legacy IRQs are inverted before
reaching the interrupt controller pin), resulting in IRQ allocation
failures such as:
genirq: Setting trigger mode 8 for irq 18 failed (gic_set_type+0x0/0x48)
Change the default polarity for PCI legacy IRQs to high on systems
booting wth ACPI on platforms with a GIC interrupt controller model,
fixing the discrepancy between specification and HW behaviour.
Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Tested-by: Duc Dang <dhdang@apm.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2016-09-05 14:12:38 +00:00
|
|
|
ACPI_ACTIVE_HIGH : ACPI_ACTIVE_LOW;
|
2005-08-05 04:44:28 +00:00
|
|
|
char *link = NULL;
|
2008-06-27 14:45:39 +00:00
|
|
|
char link_desc[16];
|
2005-08-05 04:44:28 +00:00
|
|
|
int rc;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2005-11-03 00:24:35 +00:00
|
|
|
pin = dev->pin;
|
2005-04-16 22:20:36 +00:00
|
|
|
if (!pin) {
|
2021-02-19 18:15:27 +00:00
|
|
|
dev_dbg(&dev->dev, "No interrupt pin configured\n");
|
2006-06-27 04:41:40 +00:00
|
|
|
return 0;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2016-02-17 18:26:38 +00:00
|
|
|
if (dev->irq_managed && dev->irq > 0)
|
2014-10-27 05:21:42 +00:00
|
|
|
return 0;
|
|
|
|
|
2008-12-09 04:31:01 +00:00
|
|
|
entry = acpi_pci_irq_lookup(dev, pin);
|
2008-12-09 04:31:16 +00:00
|
|
|
if (!entry) {
|
2008-01-11 03:49:58 +00:00
|
|
|
/*
|
|
|
|
* IDE legacy mode controller IRQs are magic. Why do compat
|
|
|
|
* extensions always make such a nasty mess.
|
|
|
|
*/
|
|
|
|
if (dev->class >> 8 == PCI_CLASS_STORAGE_IDE &&
|
|
|
|
(dev->class & 0x05) == 0)
|
|
|
|
return 0;
|
|
|
|
}
|
2008-12-09 04:31:16 +00:00
|
|
|
|
2008-12-09 04:31:32 +00:00
|
|
|
if (entry) {
|
|
|
|
if (entry->link)
|
|
|
|
gsi = acpi_pci_link_allocate_irq(entry->link,
|
|
|
|
entry->index,
|
|
|
|
&triggering, &polarity,
|
|
|
|
&link);
|
|
|
|
else
|
|
|
|
gsi = entry->index;
|
|
|
|
} else
|
2008-12-09 04:31:16 +00:00
|
|
|
gsi = -1;
|
|
|
|
|
2008-12-09 04:30:26 +00:00
|
|
|
if (gsi < 0) {
|
x86/ACPI/PCI: Recognize that Interrupt Line 255 means "not connected"
Per the x86-specific footnote to PCI spec r3.0, sec 6.2.4, the value 255 in
the Interrupt Line register means "unknown" or "no connection."
Previously, when we couldn't derive an IRQ from the _PRT, we fell back to
using the value from Interrupt Line as an IRQ. It's questionable whether
we should do that at all, but the spec clearly suggests we shouldn't do it
for the value 255 on x86.
Calling request_irq() with IRQ 255 may succeed, but the driver won't
receive any interrupts. Or, if IRQ 255 is shared with another device, it
may succeed, and the driver's ISR will be called at random times when the
*other* device interrupts. Or it may fail if another device is using IRQ
255 with incompatible flags. What we *want* is for request_irq() to fail
predictably so the driver can fall back to polling.
On x86, assume 255 in the Interrupt Line means the INTx line is not
connected. In that case, set dev->irq to IRQ_NOTCONNECTED so request_irq()
will fail gracefully with -ENOTCONN.
We found this problem on a system where Secure Boot firmware assigned
Interrupt Line 255 to an i801_smbus device and another device was already
using MSI-X IRQ 255. This was in v3.10, where i801_probe() fails if
request_irq() fails:
i801_smbus 0000:00:1f.3: enabling device (0140 -> 0143)
i801_smbus 0000:00:1f.3: can't derive routing for PCI INT C
i801_smbus 0000:00:1f.3: PCI INT C: no GSI
genirq: Flags mismatch irq 255. 00000080 (i801_smbus) vs. 00000000 (megasa)
CPU: 0 PID: 2487 Comm: kworker/0:1 Not tainted 3.10.0-229.el7.x86_64 #1
Hardware name: FUJITSU PRIMEQUEST 2800E2/D3736, BIOS PRIMEQUEST 2000 Serie5
Call Trace:
dump_stack+0x19/0x1b
__setup_irq+0x54a/0x570
request_threaded_irq+0xcc/0x170
i801_probe+0x32f/0x508 [i2c_i801]
local_pci_probe+0x45/0xa0
i801_smbus 0000:00:1f.3: Failed to allocate irq 255: -16
i801_smbus: probe of 0000:00:1f.3 failed with error -16
After aeb8a3d16ae0 ("i2c: i801: Check if interrupts are disabled"),
i801_probe() will fall back to polling if request_irq() fails. But we
still need this patch because request_irq() may succeed or fail depending
on other devices in the system. If request_irq() fails, i801_smbus will
work by falling back to polling, but if it succeeds, i801_smbus won't work
because it expects interrupts that it may not receive.
Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2016-02-15 04:52:01 +00:00
|
|
|
/*
|
|
|
|
* No IRQ known to the ACPI subsystem - maybe the BIOS /
|
|
|
|
* driver reported one, then use it. Exit in any case.
|
|
|
|
*/
|
2019-08-21 03:44:19 +00:00
|
|
|
if (!acpi_pci_irq_valid(dev, pin)) {
|
|
|
|
kfree(entry);
|
x86/ACPI/PCI: Recognize that Interrupt Line 255 means "not connected"
Per the x86-specific footnote to PCI spec r3.0, sec 6.2.4, the value 255 in
the Interrupt Line register means "unknown" or "no connection."
Previously, when we couldn't derive an IRQ from the _PRT, we fell back to
using the value from Interrupt Line as an IRQ. It's questionable whether
we should do that at all, but the spec clearly suggests we shouldn't do it
for the value 255 on x86.
Calling request_irq() with IRQ 255 may succeed, but the driver won't
receive any interrupts. Or, if IRQ 255 is shared with another device, it
may succeed, and the driver's ISR will be called at random times when the
*other* device interrupts. Or it may fail if another device is using IRQ
255 with incompatible flags. What we *want* is for request_irq() to fail
predictably so the driver can fall back to polling.
On x86, assume 255 in the Interrupt Line means the INTx line is not
connected. In that case, set dev->irq to IRQ_NOTCONNECTED so request_irq()
will fail gracefully with -ENOTCONN.
We found this problem on a system where Secure Boot firmware assigned
Interrupt Line 255 to an i801_smbus device and another device was already
using MSI-X IRQ 255. This was in v3.10, where i801_probe() fails if
request_irq() fails:
i801_smbus 0000:00:1f.3: enabling device (0140 -> 0143)
i801_smbus 0000:00:1f.3: can't derive routing for PCI INT C
i801_smbus 0000:00:1f.3: PCI INT C: no GSI
genirq: Flags mismatch irq 255. 00000080 (i801_smbus) vs. 00000000 (megasa)
CPU: 0 PID: 2487 Comm: kworker/0:1 Not tainted 3.10.0-229.el7.x86_64 #1
Hardware name: FUJITSU PRIMEQUEST 2800E2/D3736, BIOS PRIMEQUEST 2000 Serie5
Call Trace:
dump_stack+0x19/0x1b
__setup_irq+0x54a/0x570
request_threaded_irq+0xcc/0x170
i801_probe+0x32f/0x508 [i2c_i801]
local_pci_probe+0x45/0xa0
i801_smbus 0000:00:1f.3: Failed to allocate irq 255: -16
i801_smbus: probe of 0000:00:1f.3 failed with error -16
After aeb8a3d16ae0 ("i2c: i801: Check if interrupts are disabled"),
i801_probe() will fall back to polling if request_irq() fails. But we
still need this patch because request_irq() may succeed or fail depending
on other devices in the system. If request_irq() fails, i801_smbus will
work by falling back to polling, but if it succeeds, i801_smbus won't work
because it expects interrupts that it may not receive.
Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2016-02-15 04:52:01 +00:00
|
|
|
return 0;
|
2019-08-21 03:44:19 +00:00
|
|
|
}
|
x86/ACPI/PCI: Recognize that Interrupt Line 255 means "not connected"
Per the x86-specific footnote to PCI spec r3.0, sec 6.2.4, the value 255 in
the Interrupt Line register means "unknown" or "no connection."
Previously, when we couldn't derive an IRQ from the _PRT, we fell back to
using the value from Interrupt Line as an IRQ. It's questionable whether
we should do that at all, but the spec clearly suggests we shouldn't do it
for the value 255 on x86.
Calling request_irq() with IRQ 255 may succeed, but the driver won't
receive any interrupts. Or, if IRQ 255 is shared with another device, it
may succeed, and the driver's ISR will be called at random times when the
*other* device interrupts. Or it may fail if another device is using IRQ
255 with incompatible flags. What we *want* is for request_irq() to fail
predictably so the driver can fall back to polling.
On x86, assume 255 in the Interrupt Line means the INTx line is not
connected. In that case, set dev->irq to IRQ_NOTCONNECTED so request_irq()
will fail gracefully with -ENOTCONN.
We found this problem on a system where Secure Boot firmware assigned
Interrupt Line 255 to an i801_smbus device and another device was already
using MSI-X IRQ 255. This was in v3.10, where i801_probe() fails if
request_irq() fails:
i801_smbus 0000:00:1f.3: enabling device (0140 -> 0143)
i801_smbus 0000:00:1f.3: can't derive routing for PCI INT C
i801_smbus 0000:00:1f.3: PCI INT C: no GSI
genirq: Flags mismatch irq 255. 00000080 (i801_smbus) vs. 00000000 (megasa)
CPU: 0 PID: 2487 Comm: kworker/0:1 Not tainted 3.10.0-229.el7.x86_64 #1
Hardware name: FUJITSU PRIMEQUEST 2800E2/D3736, BIOS PRIMEQUEST 2000 Serie5
Call Trace:
dump_stack+0x19/0x1b
__setup_irq+0x54a/0x570
request_threaded_irq+0xcc/0x170
i801_probe+0x32f/0x508 [i2c_i801]
local_pci_probe+0x45/0xa0
i801_smbus 0000:00:1f.3: Failed to allocate irq 255: -16
i801_smbus: probe of 0000:00:1f.3 failed with error -16
After aeb8a3d16ae0 ("i2c: i801: Check if interrupts are disabled"),
i801_probe() will fall back to polling if request_irq() fails. But we
still need this patch because request_irq() may succeed or fail depending
on other devices in the system. If request_irq() fails, i801_smbus will
work by falling back to polling, but if it succeeds, i801_smbus won't work
because it expects interrupts that it may not receive.
Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2016-02-15 04:52:01 +00:00
|
|
|
|
2014-02-20 13:27:46 +00:00
|
|
|
if (acpi_isa_register_gsi(dev))
|
2012-11-21 13:46:04 +00:00
|
|
|
dev_warn(&dev->dev, "PCI INT %c: no GSI\n",
|
|
|
|
pin_name(pin));
|
2013-02-16 18:58:34 +00:00
|
|
|
|
2014-02-10 13:00:11 +00:00
|
|
|
kfree(entry);
|
2012-11-21 13:46:04 +00:00
|
|
|
return 0;
|
2005-08-05 04:44:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-04-28 01:01:20 +00:00
|
|
|
rc = acpi_register_gsi(&dev->dev, gsi, triggering, polarity);
|
2005-07-28 18:42:00 +00:00
|
|
|
if (rc < 0) {
|
2008-06-27 14:45:39 +00:00
|
|
|
dev_warn(&dev->dev, "PCI INT %c: failed to register GSI\n",
|
2008-12-09 04:30:36 +00:00
|
|
|
pin_name(pin));
|
2013-02-16 18:58:34 +00:00
|
|
|
kfree(entry);
|
2006-06-27 04:41:40 +00:00
|
|
|
return rc;
|
2005-07-28 18:42:00 +00:00
|
|
|
}
|
2016-02-17 18:26:38 +00:00
|
|
|
dev->irq = rc;
|
|
|
|
dev->irq_managed = 1;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
if (link)
|
2008-06-27 14:45:39 +00:00
|
|
|
snprintf(link_desc, sizeof(link_desc), " -> Link[%s]", link);
|
|
|
|
else
|
|
|
|
link_desc[0] = '\0';
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2011-12-05 19:51:18 +00:00
|
|
|
dev_dbg(&dev->dev, "PCI INT %c%s -> GSI %u (%s, %s) -> IRQ %d\n",
|
|
|
|
pin_name(pin), link_desc, gsi,
|
|
|
|
(triggering == ACPI_LEVEL_SENSITIVE) ? "level" : "edge",
|
|
|
|
(polarity == ACPI_ACTIVE_LOW) ? "low" : "high", dev->irq);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
kfree(entry);
|
2006-06-27 04:41:40 +00:00
|
|
|
return 0;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2005-08-05 04:44:28 +00:00
|
|
|
void acpi_pci_irq_disable(struct pci_dev *dev)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2008-12-09 04:31:01 +00:00
|
|
|
struct acpi_prt_entry *entry;
|
2008-12-09 04:31:37 +00:00
|
|
|
int gsi;
|
|
|
|
u8 pin;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2005-11-03 00:24:35 +00:00
|
|
|
pin = dev->pin;
|
2016-02-17 18:26:38 +00:00
|
|
|
if (!pin || !dev->irq_managed || dev->irq <= 0)
|
2006-06-27 04:41:40 +00:00
|
|
|
return;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2016-02-17 18:26:42 +00:00
|
|
|
/* Keep IOAPIC pin configuration when suspending */
|
|
|
|
if (dev->dev.power.is_prepared)
|
|
|
|
return;
|
|
|
|
#ifdef CONFIG_PM
|
|
|
|
if (dev->dev.power.runtime_status == RPM_SUSPENDING)
|
|
|
|
return;
|
|
|
|
#endif
|
|
|
|
|
2008-12-09 04:31:01 +00:00
|
|
|
entry = acpi_pci_irq_lookup(dev, pin);
|
|
|
|
if (!entry)
|
2006-06-27 04:41:40 +00:00
|
|
|
return;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-12-09 04:31:32 +00:00
|
|
|
if (entry->link)
|
|
|
|
gsi = acpi_pci_link_free_irq(entry->link);
|
|
|
|
else
|
|
|
|
gsi = entry->index;
|
2008-12-09 04:31:01 +00:00
|
|
|
|
2013-02-16 18:58:34 +00:00
|
|
|
kfree(entry);
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* TBD: It might be worth clearing dev->irq by magic constant
|
|
|
|
* (e.g. PCI_UNDEFINED_IRQ).
|
|
|
|
*/
|
|
|
|
|
2011-12-05 19:51:18 +00:00
|
|
|
dev_dbg(&dev->dev, "PCI INT %c disabled\n", pin_name(pin));
|
2014-10-27 05:21:42 +00:00
|
|
|
if (gsi >= 0) {
|
2014-06-10 06:16:27 +00:00
|
|
|
acpi_unregister_gsi(gsi);
|
2016-02-17 18:26:38 +00:00
|
|
|
dev->irq_managed = 0;
|
2014-10-27 05:21:42 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|