Searched refs:MSI (Results 1 – 25 of 147) sorted by relevance
123456
| /kernel/linux/linux-5.10/Documentation/PCI/ |
| D | msi-howto.rst | 5 The MSI Driver Guide HOWTO
16 the advantages of using MSI over traditional interrupt mechanisms, how
17 to change your driver to use MSI or MSI-X and some basic diagnostics to
27 The MSI capability was first specified in PCI 2.2 and was later enhanced
28 in PCI 3.0 to allow each interrupt to be masked individually. The MSI-X
30 per device than MSI and allows interrupts to be independently configured.
32 Devices may support both MSI and MSI-X, but only one can be enabled at
73 driver has to set up the device to use MSI or MSI-X. Not all machines
80 To support MSI or MSI-X, the kernel must be built with the CONFIG_PCI_MSI
86 Using MSI
[all …]
|
| D | pci.rst | 319 With MSI and MSI-X (more below) the interrupt number is a CPU "vector".
325 MSI and MSI-X are PCI capabilities. Both are "Message Signaled Interrupts"
327 The fundamental difference between MSI and MSI-X is how multiple
328 "vectors" get allocated. MSI requires contiguous blocks of vectors
329 while MSI-X can allocate several individual ones.
331 MSI capability can be enabled by calling pci_alloc_irq_vectors() with the
335 support MSI or MSI-X and a call to pci_alloc_irq_vectors with just
339 Drivers that have different interrupt handlers for MSI/MSI-X and
344 There are (at least) two really good reasons for using MSI:
346 1) MSI is an exclusive interrupt vector by definition.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/PCI/endpoint/ |
| D | pci-test-howto.rst | 79 to change the vendorid and the number of MSI interrupts used by the function
158 SET IRQ TYPE TO MSI: OKAY
191 SET IRQ TYPE TO MSI-X: OKAY
192 MSI-X1: OKAY
193 MSI-X2: OKAY
194 MSI-X3: OKAY
195 MSI-X4: OKAY
196 MSI-X5: OKAY
197 MSI-X6: OKAY
198 MSI-X7: OKAY
[all …]
|
| D | pci-test-function.rst | 45 Bit 1 raise MSI IRQ
46 Bit 2 raise MSI-X IRQ
82 This register contains the interrupt type (Legacy/MSI) triggered
83 for the READ/WRITE/COPY and raise IRQ (Legacy/MSI) commands.
89 MSI 1
90 MSI-X 2
101 MSI [1 .. 32]
102 MSI-X [1 .. 2048]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 1 This document describes the generic device tree binding for MSI controllers and
9 those busses to the MSI controllers which they are capable of using,
17 they can address. An MSI controller may feature a number of doorbells.
22 MSI controllers may have restrictions on permitted payloads.
28 MSI controller and device rather than a property of either in isolation).
31 MSI controllers:
34 An MSI controller signals interrupts to a CPU when a write is made to an MMIO
35 address by some master. An MSI controller may feature a number of doorbells.
40 - msi-controller: Identifies the node as an MSI controller.
51 the specific MSI controller.
[all …]
|
| D | fsl,ls-scfg-msi.txt | 1 * Freescale Layerscape SCFG PCIe MSI controller
6 Layerscape PCIe MSI controller block such as:
12 - msi-controller: indicates that this is a PCIe MSI controller node
21 MSI controller node
|
| D | al,alpine-msix.txt | 3 See arm,gic-v3.txt for SPI and MSI definitions.
12 - al,msi-base-spi: SPI base of the MSI frame
13 - al,msi-num-spis: number of SPIs assigned to the MSI frame, relative to SPI0
|
| D | marvell,odmi-controller.txt | 2 * Marvell ODMI for MSI support
5 which can be used by on-board peripheral for MSI interrupts.
15 - msi-controller : Identifies the node as an MSI controller.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/ |
| D | brcm,iproc-pcie.txt | 44 MSI support (optional):
46 For older platforms without MSI integrated in the GIC, iProc PCIe core provides
47 an event queue based MSI support. The iProc MSI uses host memories to store
48 MSI posted writes in the event queues
50 On newer iProc platforms, gicv2m or gicv3-its based MSI support should be used
52 - msi-map: Maps a Requester ID to an MSI controller and associated MSI
55 - msi-parent: Link to the device node of the MSI controller, used when no MSI
56 sideband data is passed between the iProc PCIe controller and the MSI
64 When the iProc event queue based MSI is used, one needs to define the
65 following properties in the MSI device node:
[all …]
|
| D | pci-msi.txt | 2 relationship between PCI devices and MSI controllers.
18 Requester ID. A mechanism is required to associate a device with both the MSI
22 For generic MSI bindings, see
32 - msi-map: Maps a Requester ID to an MSI controller and associated
38 * msi-controller is a single phandle to an MSI controller
52 - msi-parent: Describes the MSI parent of the root complex itself. Where
53 the root complex and MSI controller do not pass sideband data with MSI
54 writes, this property may be used to describe the MSI controller(s)
79 * The sideband data provided to the MSI controller is
107 * The sideband data provided to the MSI controller is
[all …]
|
| D | xgene-pci-msi.txt | 1 * AppliedMicro X-Gene v1 PCIe MSI controller
6 X-Gene v1 PCIe MSI controller block.
7 - msi-controller: indicates that this is an X-Gene v1 PCIe MSI controller node
9 registers. These registers include the MSI termination address and data
10 registers as well as the MSI interrupt status registers.
16 Each PCIe node needs to have property msi-parent that points to an MSI
23 + MSI node:
46 + PCIe controller node with msi-parent property pointing to MSI node:
|
| D | layerscape-pcie-gen4.txt | 17 none MSI/MSI-X/INTx mode,but there is interrupt line for aer.
19 none MSI/MSI-X/INTx mode,but there is interrupt line for pme.
23 - msi-parent : See the generic MSI binding described in
|
| D | tango-pcie.txt | 13 - interrupts: spec for misc interrupts, spec for MSI
28 <55 IRQ_TYPE_LEVEL_HIGH>; /* MSI */
|
| /kernel/linux/linux-5.10/Documentation/misc-devices/ |
| D | pci-endpoint-test.rst | 17 #) raise MSI IRQ
18 #) raise MSI-X IRQ
36 Tests message signalled interrupts. The MSI number
39 Tests message signalled interrupts. The MSI-X number
43 should be passed as argument (0: Legacy, 1:MSI, 2:MSI-X).
|
| D | spear-pcie-gadget.rst | 42 no_of_msi zero if MSI is not enabled by host. A positive value is the
43 number of MSI vector granted.
58 INTA, MSI or NO_INT). Select MSI only when you have programmed
60 no_of_msi number of MSI vector needed.
62 send_msi write MSI vector to be sent.
142 if MSI is to be used as interrupt, program no of msi vector needed (say4)::
146 select MSI as interrupt type::
148 # echo MSI >> int_type
165 Should return 4 (number of requested MSI vector)
|
| /kernel/linux/linux-5.10/drivers/ntb/ |
| D | Kconfig | 17 bool "MSI Interrupt Support"
20 Support using MSI interrupt forwarding instead of (or in addition to)
21 hardware doorbells. MSI interrupts typically offer lower latency
22 than doorbells and more MSI interrupts can be made available to
24 in the hardware driver for creating the MSI interrupts.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mailbox/ |
| D | brcm,iproc-flexrm-mbox.txt | 14 - msi-parent: Phandles (and potential Device IDs) to MSI controllers
16 interrupts) to CPU. There is one MSI for each FlexRM ring.
23 The 2nd cell contains MSI completion threshold. This is the
25 one MSI interrupt to CPU.
27 The 3nd cell contains MSI timer value representing time for
31 specified by this cell then it will inject one MSI interrupt
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | msi-pic.txt | 1 * 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.
27 optional, without this, all the MSI interrupts can be used.
29 no splitting an individual MSI register or the associated PIC interrupt).
34 is used for MSI messaging. The address of MSIIR in PCI address space is
35 the MSI message address.
84 Freescale MSI driver calculates the address of MSIIR (in the MSI register
85 block) and sets that address as the MSI message address.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | hsta.txt | 10 Currently only the MSI support is used by Linux using the following
15 - reg : register mapping for the HSTA MSI space
16 - interrupts : ordered interrupt mapping for each MSI in the register
|
| /kernel/linux/linux-5.10/drivers/ntb/test/ |
| D | Kconfig | 31 tristate "NTB MSI Test Client"
34 This tool demonstrates the use of the NTB MSI library to
35 send MSI interrupts between peers.
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | configfs-spear-pcie-gadget | 22 no_of_msi used to configure number of MSI vector needed and
23 to read no of MSI granted.
25 send_msi write MSI vector to be sent.
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/neterion/ |
| D | s2io.rst | 22 such as jumbo frames, MSI/MSI-X, checksum offloads, TSO, UFO and so on.
46 driver version, interface name(eth3, eth4), Interrupt type(INTA, MSI, MSI-X).
66 d. MSI/MSI-X. Can be enabled on platforms which support this feature
108 Specifies interrupt type. Possible values 0(INTA), 2(MSI-X)
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | dvb-usb-m920x-cardlist.rst | 21 * - MSI DIGI VOX mini II DVB-T USB2.0
23 * - MSI Mega Sky 580 DVB-T USB2.0
|
| /kernel/linux/linux-5.10/drivers/media/pci/ddbridge/ |
| D | Kconfig | 35 bool "Enable Message Signaled Interrupts (MSI) per default (EXPERIMENTAL)"
39 Use PCI MSI (Message Signaled Interrupts) per default. Enabling this
42 module. MSI can still be disabled by passing msi=0 as option, as
|
| /kernel/linux/linux-5.10/Documentation/PCI/endpoint/function/binding/ |
| D | pci-test.rst | 22 msi_interrupts Should be 1 to 32 depending on the number of MSI interrupts
24 msix_interrupts Should be 1 to 2048 depending on the number of MSI-X
|
123456