Home
last modified time | relevance | path

Searched refs:MSI (Results 1 – 71 of 71) sorted by relevance

/linux-4.1.27/Documentation/PCI/
DMSI-HOWTO.txt1 The MSI Driver Guide HOWTO
13 the advantages of using MSI over traditional interrupt mechanisms, how
14 to change your driver to use MSI or MSI-X and some basic diagnostics to
23 The MSI capability was first specified in PCI 2.2 and was later enhanced
24 in PCI 3.0 to allow each interrupt to be masked individually. The MSI-X
26 per device than MSI and allows interrupts to be independently configured.
28 Devices may support both MSI and MSI-X, but only one can be enabled at
67 driver has to set up the device to use MSI or MSI-X. Not all machines
73 To support MSI or MSI-X, the kernel must be built with the CONFIG_PCI_MSI
79 4.2 Using MSI
[all …]
D00-INDEX3 MSI-HOWTO.txt
4 - the Message Signaled Interrupts (MSI) Driver Guide HOWTO and FAQ.
DPCIEBUS-HOWTO.txt164 6.1 MSI Vector Resource
166 The MSI capability structure enables a device software driver to call
167 pci_enable_msi to request MSI based interrupts. Once MSI interrupts
169 calls pci_disable_msi to disable MSI interrupts and revert back to
175 request MSI based interrupts. A service driver may not know whether
190 6.2 MSI-X Vector Resources
192 Similar to the MSI a device driver for an MSI-X capable device can
193 call pci_enable_msix to request MSI-X interrupts. All service drivers
Dpci.txt374 With MSI and MSI-X (more below) the interrupt number is a CPU "vector".
380 MSI and MSI-X are PCI capabilities. Both are "Message Signaled Interrupts"
382 The fundamental difference between MSI and MSI-X is how multiple
383 "vectors" get allocated. MSI requires contiguous blocks of vectors
384 while MSI-X can allocate several individual ones.
386 MSI capability can be enabled by calling pci_enable_msi() or
391 If your PCI device supports both, try to enable MSI-X first.
393 or BIOSes do NOT support MSI or MSI-X and the call to pci_enable_msi/msix
395 two (or more) interrupt handlers: one for MSI/MSI-X and another for IRQs.
399 There are (at least) two really good reasons for using MSI:
[all …]
Dpci-error-recovery.txt295 memory mapped I/O space and DMA. Interrupts (Legacy, MSI, or MSI-X)
/linux-4.1.27/Documentation/misc-devices/
Dspear-pcie-gadget.txt35 no_of_msi :zero if MSI is not enabled by host. A positive value is the
36 number of MSI vector granted.
48 INTA, MSI or NO_INT). Select MSI only when you have programmed
50 no_of_msi :number of MSI vector needed.
52 send_msi :write MSI vector to be sent.
110 if MSI is to be used as interrupt, program no of msi vector needed (say4)
113 select MSI as interrupt type
114 # echo MSI >> int_type
126 Should return 4 (number of requested MSI vector)
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Dmsi-pic.txt1 * Freescale MSI interrupt controller
8 version is 4.3, the number of MSI registers is increased to 16, MSIIR1 is
17 region must be added because different MSI group has different MSIIR1 offset.
32 optional, without this, all the MSI interrupts can be used.
34 no splitting an individual MSI register or the associated PIC interrupt).
39 is used for MSI messaging. The address of MSIIR in PCI address space is
40 the MSI message address.
89 Freescale MSI driver calculates the address of MSIIR (in the MSI register
90 block) and sets that address as the MSI message address.
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/4xx/
Dhsta.txt10 Currently only the MSI support is used by Linux using the following
15 - reg : register mapping for the HSTA MSI space
17 - interrupts : ordered interrupt mapping for each MSI in the register
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dgic.txt102 * GICv2m extension for MSI/MSI-x support (Optional)
104 Certain revisions of GIC-400 supports MSI/MSI-x via V2M register frame(s).
111 - msi-controller : Identifies the node as an MSI controller.
113 - reg : GICv2m MSI interface register base and size
119 the MSI frame, overriding the HW value.
Dgic-v3.txt55 used to route Message Signalled Interrupts (MSI) to the CPUs.
59 - msi-controller : Boolean property. Identifies the node as an MSI controller
/linux-4.1.27/Documentation/networking/
Ds2io.txt16 such as jumbo frames, MSI/MSI-X, checksum offloads, TSO, UFO and so on.
32 driver version, interface name(eth3, eth4), Interrupt type(INTA, MSI, MSI-X).
51 d. MSI/MSI-X. Can be enabled on platforms which support this feature
83 Specifies interrupt type. Possible values 0(INTA), 2(MSI-X)
Digb.txt85 In this mode, a separate MSI-X vector is allocated for each queue and one
92 REQUIREMENTS: MSI-X support is required for Multiqueue. If MSI-X is not
93 found, the system will fallback to MSI or to Legacy interrupts.
De1000e.txt212 Valid Range: 0-2 (0=legacy, 1=MSI, 2=MSI-X)
218 interrupt order is MSI-X, MSI, Legacy. If specifying MSI (IntMode=1)
219 interrupts, only MSI and Legacy will be attempted.
Di40evf.txt20 The guest OS loading the i40evf driver must support MSI-X interrupts.
Dixgbevf.txt23 The guest OS loading the ixgbevf driver must support MSI-X interrupts.
Dvxge.txt49 vi) MSI-X: (Enabled by default)
Digbvf.txt25 The guest OS loading the igbvf driver must support MSI-X interrupts.
Dixgbe.txt325 model for the guests, and this older CPU model does not support MSI-X
Dscaling.txt70 signaling path for PCIe devices uses message signaled interrupts (MSI-X),
/linux-4.1.27/Documentation/ABI/testing/
Dconfigfs-spear-pcie-gadget21 no_of_msi ... used to configure number of MSI vector needed and
22 to read no of MSI granted.
24 send_msi ... write MSI vector to be sent.
Dsysfs-bus-pci72 Writing a zero value to this attribute disallows MSI and
73 MSI-X for any future drivers of the device. If the device
74 is a bridge, MSI and MSI-X will be disallowed for future
/linux-4.1.27/drivers/pci/
DKconfig9 bool "Message Signaled Interrupts (MSI and MSI-X)"
13 This allows device drivers to enable MSI (Message Signaled
18 Use of PCI MSI interrupts can be disabled at kernel boot time
19 by using the 'pci=nomsi' option. This disables MSI for the
/linux-4.1.27/drivers/pci/host/
Dpci-dra7xx.c56 #define MSI BIT(4) macro
133 ~LEG_EP_INTERRUPTS & ~MSI); in dra7xx_pcie_enable_interrupts()
137 PCIECTRL_DRA7XX_CONF_IRQENABLE_SET_MSI, MSI); in dra7xx_pcie_enable_interrupts()
202 case MSI: in dra7xx_pcie_msi_irq_handler()
/linux-4.1.27/Documentation/devicetree/bindings/pci/
Dpci-keystone.txt18 pcie_msi_intc : Interrupt controller device node for MSI IRQ chip
21 interrupts: GIC interrupt lines connected to PCI MSI interrupt lines
Dfsl,imx6q-pcie.txt12 - "msi": The interrupt that is asserted when an MSI is received
Drcar-pci.txt13 - interrupts: two interrupt sources for MSI interrupts, followed by interrupt
Dti-pci.txt16 main interrupt line and the second for MSI interrupt line.
Dxilinx-pcie.txt33 The core provides a single interrupt for both INTx/MSI messages. So,
Dnvidia,tegra20-pcie.txt19 "msi": The Tegra interrupt that is asserted when an MSI is received
137 0 99 0x04>; /* MSI interrupt */
/linux-4.1.27/arch/sparc/kernel/
Dpci_fire.c128 #define MSI_MAP(MSI) (0x020000UL + (MSI) * 0x8UL) argument
133 #define MSI_CLEAR(MSI) (0x028000UL + (MSI) * 0x8UL) argument
/linux-4.1.27/kernel/irq/
DKconfig63 # Generic MSI interrupt support
67 # Generic MSI hierarchical interrupt domain support
/linux-4.1.27/Documentation/video4linux/
DCARDLIST.em28xx6 5 -> MSI VOX USB 2.0 (em2820/em2840)
50 49 -> MSI DigiVox A/D (em2880) [eb1a:e310]
51 50 -> MSI DigiVox A/D II (em2880) [eb1a:e320]
DCARDLIST.saa713456 55 -> LifeView FlyDVB-T DUO / MSI TV@nywhere Duo [5168:0306,4E42:0306]
83 82 -> MSI TV@Anywhere plus [1462:6231,1462:8624]
95 …94 -> LifeView FlyDVB-T Hybrid Cardbus/MSI TV @nywhere A/D NB [5168:3306,5168:3502,5168:3307,4e42:…
136 135 -> MSI TV@nywhere A/D v1.1 [1462:8625]
DCARDLIST.cx888 7 -> MSI TV-@nywhere Master [1462:8606]
14 13 -> MSI TV-@nywhere
/linux-4.1.27/arch/mips/pci/
Dpci-vr41xx.h108 #define MSI 0x1U macro
/linux-4.1.27/arch/powerpc/boot/dts/
Dakebono.dts267 /* Inbound starting at 0x0 to 0x40000000000. In order to use MSI
307 /* Inbound starting at 0x0 to 0x40000000000. In order to use MSI
347 /* Inbound starting at 0x0 to 0x40000000000. In order to use MSI
387 /* Inbound starting at 0x0 to 0x40000000000. In order to use MSI
Dbluestone.dts385 MSI: ppc4xx-msi@C10000000 { label
393 interrupt-parent = <&MSI>;
Dredwood.dts361 MSI: ppc4xx-msi@400300000 { label
Dkilauea.dts407 MSI: ppc4xx-msi@C10000000 { label
Dkatmai.dts445 MSI: ppc4xx-msi@400300000 { label
Dcanyonlands.dts539 MSI: ppc4xx-msi@C10000000 { label
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-driver-ib_srp58 MSI-X completion vector of the first RDMA channel. Some
59 HCA's allocate multiple (n) MSI-X vectors per HCA port. If
61 configured such that each MSI-X interrupt is handled by a
/linux-4.1.27/Documentation/usb/
Ddwc3.txt14 to the device. If MSI provides per-endpoint interrupt this dummy
/linux-4.1.27/Documentation/scsi/
DChangeLog.megaraid_sas54 9. Add support for Extended MSI-x vectors for Invader and Fury(12Gb/s
75 2. Add module param for configurable MSI-X vector count.
122 8. Add multiple MSI-X vector/multiple reply queue support.
138 1. Remove MSI-X black list, use MFI_REG_STATE.ready.msiEnable.
155 3. Enable MSI-X before calling megasas_init_fw().
157 boards in MSI-X mode.
177 3. Add MSI-X support and 'msix_disable' module parameter.
/linux-4.1.27/Documentation/virtual/kvm/devices/
Dxics.txt56 edge-sensitive (or MSI).
/linux-4.1.27/drivers/net/ethernet/intel/
DKconfig252 will be called ixgbevf. MSI-X interrupt support is required
322 will be called i40evf. MSI-X interrupt support is required
343 will be called fm10k. MSI-X interrupt support is required
/linux-4.1.27/drivers/platform/x86/
DKconfig247 tristate "MSI Laptop Extras"
254 This is a driver for laptops built by MSI (MICRO-STAR
257 MSI MegaBook S270 (MS-1013)
265 If you have an MSI S270 laptop, say Y or M here.
586 tristate "MSI WMI extras"
592 Say Y here if you want to support WMI-based hotkeys on MSI laptops.
/linux-4.1.27/drivers/net/ethernet/neterion/vxge/
Dvxge-main.h175 #define MSI 1 macro
/linux-4.1.27/drivers/media/usb/dvb-usb-v2/
DKconfig100 Say Y here to support the MSI Megasky 580 (55801) DVB-T USB2.0
/linux-4.1.27/Documentation/i2c/busses/
Di2c-ali15x357 Microstar (MSI) MS-5169
/linux-4.1.27/Documentation/sound/alsa/
DHD-Audio.txt129 HD-audio driver uses MSI as default (if available) since 2.6.33
130 kernel as MSI works better on some machines, and in general, it's
132 regressions with MSI (especially in a combination with AMD chipset),
133 thus we disabled MSI for them.
135 There seem also still other devices that don't work with MSI. If you
138 MSI. If it works, you can add the known bad device to the blacklist
DALSA-Configuration.txt890 enable_msi - Enable Message Signaled Interrupt (MSI) (default = off)
1965 Note: on some SMP motherboards like MSI 694D the interrupts might
/linux-4.1.27/arch/s390/
DKconfig523 int "Maximum number of MSI interrupts (64-32768)"
528 provide for MSI interrupts. If you configure your system to have
529 too few drivers will fail to allocate MSI interrupts for all
/linux-4.1.27/drivers/hid/
DKconfig276 tristate "MSI GT68xR LED support"
279 Say Y here if you want to enable support for the three MSI GT68xR LEDs
287 - MSI GT683R
/linux-4.1.27/drivers/scsi/lpfc/
Dlpfc.h474 MSI, enumerator
Dlpfc_init.c8558 phba->intr_type = MSI; in lpfc_sli_enable_intr()
8591 else if (phba->intr_type == MSI) in lpfc_sli_disable_intr()
9132 phba->intr_type = MSI; in lpfc_sli4_enable_intr()
9178 else if (phba->intr_type == MSI) in lpfc_sli4_disable_intr()
/linux-4.1.27/drivers/iommu/
DKconfig171 Supports Interrupt remapping for IO-APIC and MSI devices.
/linux-4.1.27/drivers/media/usb/dvb-usb/
DKconfig143 Say Y here to support the MSI Mega Sky 580 USB2.0 DVB-T receiver.
/linux-4.1.27/arch/powerpc/
DKconfig.debug69 bool "Run self-tests of the MSI bitmap code."
/linux-4.1.27/Documentation/video4linux/bttv/
DCards904 MSI
906 MSI TV@nywhere Tuner Card (MS-8876) (CX23881/883) Not Bt878 compatible.
/linux-4.1.27/arch/arm/boot/dts/
Dtegra20.dtsi581 GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>; /* MSI interrupt */
Dtegra30.dtsi21 GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>; /* MSI interrupt */
Dtegra124.dtsi25 <GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>; /* MSI interrupt */
/linux-4.1.27/drivers/input/mouse/
DKconfig118 Say Y here if you have a laptop (such as MSI WIND Netbook)
/linux-4.1.27/Documentation/virtual/kvm/
Dapi.txt1462 Set the number of MSI-X interrupts for an assigned device. The number is
1463 reset again by terminating the MSI-X assignment of the device via
1484 Specifies the routing of an MSI-X assigned device interrupt to a GSI. Setting
1490 __u16 entry; /* The index of entry in the MSI-X table */
2114 Returns: >0 on delivery, 0 if guest blocked the MSI, and -1 on error
2116 Directly inject a MSI message. Only valid with in-kernel irqchip that handles
2117 MSI messages.
/linux-4.1.27/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt56 address and MSI value, will result in one of the 2048 interrupts per
/linux-4.1.27/drivers/input/touchscreen/
DKconfig318 found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
/linux-4.1.27/Documentation/
Dkernel-parameters.txt88 MSI Message Signaled Interrupts (PCI).
2673 nomsi [MSI] If the PCI_MSI kernel config parameter is
2675 disable the use of MSI interrupts system-wide.
2814 nomsi Do not use MSI for PCI Express Native Hotplug (this
2827 nomsi Do not use MSI for native PCIe PME signaling (this makes
/linux-4.1.27/drivers/eisa/
Deisa.ids795 ISA4010 "Dialogic DTI/2xx, DMX, MSI/C Adapter"
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic79xx.reg1221 * PCI Status for MSI Master DMA Transfer
/linux-4.1.27/
DMAINTAINERS6553 MSI LAPTOP SUPPORT
6559 MSI WMI SUPPORT