Home
last modified time | relevance | path

Searched refs:INTx (Results 1 – 11 of 11) sorted by relevance

/Linux-v5.4/Documentation/devicetree/bindings/pci/
Dxilinx-pcie.txt33 The core provides a single interrupt for both INTx/MSI messages. So,
36 the four INTx interrupts in ISR and route them to this domain.
Drockchip-pcie-host.txt66 The core controller provides a single interrupt for legacy INTx. The PCIe node
69 INTx interrupts are decoded and routed.
/Linux-v5.4/Documentation/PCI/
Dacpi-info.rst14 INTx interrupts (using _PRT).
21 or if the device has INTx interrupts connected by platform interrupt
Dpci.rst340 legacy INTx should chose the right one based on the msi_enabled
/Linux-v5.4/Documentation/x86/
Dearlyprintk.rst28 …tus: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
/Linux-v5.4/Documentation/driver-api/
Dvfio-mediated-device.rst372 <TAbort- <MAbort- >SERR- <PERR- INTx-
/Linux-v5.4/drivers/scsi/lpfc/
Dlpfc.h536 INTx, enumerator
Dlpfc_init.c10525 phba->intr_type = INTx; in lpfc_sli_enable_intr()
11143 phba->intr_type = INTx; in lpfc_sli4_enable_intr()
Dlpfc_sli.c418 if ((q->phba->intr_type == INTx) && (arm == LPFC_QUEUE_REARM)) in lpfc_sli4_write_eq_db()
451 if ((q->phba->intr_type == INTx) && (arm == LPFC_QUEUE_REARM)) in lpfc_sli4_if6_write_eq_db()
/Linux-v5.4/arch/x86/
DKconfig1116 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
/Linux-v5.4/Documentation/admin-guide/
Dkernel-parameters.txt3579 all PCIe root ports use INTx for all services).