| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | msi.txt | 4 Message Signaled Interrupts (MSIs) are a class of interrupts generated by a
7 MSIs were originally specified by PCI (and are used with PCIe), but may also be
12 MSIs are distinguished by some combination of:
57 MSI clients are devices which generate MSIs. For each MSI they wish to
67 This property is unordered, and MSIs may be allocated from any combination of
70 If a device has restrictions on the allocation of MSIs, these restrictions
75 and the set of MSIs they can potentially generate.
112 /* Can only generate MSIs to msi_a */
121 * Can generate MSIs to either A or B.
131 * Can generate MSIs to all of the MSI controllers.
|
| H A D | marvell,ap806-sei.yaml | 18 and is wired while a second set comes from the CPs by the mean of MSIs.
|
| /linux/arch/powerpc/platforms/pseries/ |
| H A D | msi.c | 95 pr_debug("rtas_msi: Setting MSIs to 0 failed!\n"); in rtas_disable_msi()
138 pr_debug("rtas_msi: %s requests < %d MSIs\n", prop_name, nvec); in check_req()
315 * use the remainder as spare MSIs for anyone that wants them. */ in msi_quota_for_device()
338 * fact that we using RTAS for MSIs, we don't have the 32 bit MSI RTAS in rtas_hack_32bit_msi_gen2()
662 pr_err("PCI: failed to find MSIs for bridge %pOF (domain %d)\n", in pseries_msi_allocate_domains()
678 /* No LSI -> leave MSIs (if any) configured */ in rtas_msi_pci_irq_fixup()
684 /* No MSI -> MSIs can't have been assigned by fw, leave LSI */ in rtas_msi_pci_irq_fixup()
|
| /linux/Documentation/devicetree/bindings/pci/ |
| H A D | apple,pcie.yaml | 30 MSIs are handled by the PCIe controller and translated into regular
31 interrupts. A range of 32 MSIs is provided. These 32 MSIs can be
|
| /linux/Documentation/arch/powerpc/ |
| H A D | pci_iov_resource_on_powernv.rst | 24 partitions (i.e., filtering of DMA, MSIs etc.) and to provide a mechanism
33 return all 1's value. MSIs are also blocked. There's a bit more state that
52 For DMA, MSIs and inbound PCIe error messages, we have a table (in
63 - For MSIs, we have two windows in the address space (one at the top of
91 reserved for MSIs but this is not a problem at this point; we just
152 "master PE" which is the one used for DMA, MSIs, etc., and "secondary
|
| /linux/drivers/irqchip/ |
| H A D | irq-loongson-pch-msi.c | 26 u32 irq_first; /* The vector number that MSIs starts */
27 u32 num_irqs; /* The number of vectors for MSIs */
194 pr_debug("Registering %d MSIs, starting at %d\n", in pch_msi_init()
|
| H A D | irq-sg2042-msi.c | 31 * @irq_first: First vectors number that MSIs starts
32 * @num_irqs: Number of vectors for MSIs
33 * @irq_type: IRQ type for MSIs
|
| H A D | irq-alpine-msi.c | 35 u32 spi_first; /* The SGI number that MSIs start */
36 u32 num_spis; /* The number of SGIs for MSIs */
|
| H A D | irq-gic-v2m.c | 70 u32 spi_start; /* The SPI number that MSIs start */
71 u32 nr_spis; /* The number of SPIs for MSIs */
|
| H A D | irq-armada-370-xp.c | 164 * @msi_doorbell_mask: mask of available doorbell bits for MSIs (either PCI_MSI_DOORBELL_MASK or
168 * @doorbell_mask: doorbell mask of MSIs and IPIs, stored on suspend, restored on resume
771 /* Reconfigure doorbells for IPIs and MSIs */ in mpic_resume()
|
| /linux/Documentation/devicetree/bindings/iommu/ |
| H A D | riscv,iommu.yaml | 112 /* Example 3 (IOMMU device with MSIs) */
121 /* Example 4 (IOMMU PCIe device with MSIs) */
|
| /linux/tools/testing/selftests/vfio/ |
| H A D | vfio_pci_device_test.c | 20 * Limit the number of MSIs enabled/disabled by the test regardless of the
21 * number of MSIs the device itself supports, e.g. to avoid hitting IRTE limits.
|
| /linux/arch/x86/platform/uv/ |
| H A D | uv_irq.c | 120 * on the specified blade to allow the sending of MSIs to the specified CPU.
130 * Disable the specified MMR located on the specified blade so that MSIs are
|
| /linux/include/asm-generic/ |
| H A D | msi.h | 34 /* Device generating MSIs is proxying for another device */
|
| /linux/arch/x86/kernel/ |
| H A D | irq.c | 417 /* Posted Interrupt Descriptors for coalesced MSIs to be posted */
475 * For MSIs that are delivered as posted interrupts, the CPU notifications
476 * can be coalesced if the MSIs arrive in high frequency bursts.
|
| /linux/Documentation/virt/kvm/devices/ |
| H A D | mpic.rst | 30 MSIs may be signaled by using this attribute group to write
|
| /linux/drivers/iommu/intel/ |
| H A D | irq_remapping.c | 499 /* Block compatibility-format MSIs */ in iommu_enable_irq_remapping()
1288 * With posted MSIs, the MSI vectors are multiplexed into a single notification
1290 * MSIs are then dispatched in a demux loop that harvests the MSIs from the
1291 * CPU's Posted Interrupt Request bitmap. I.e. Posted MSIs never get sent to
1298 * For the example below, 3 MSIs are coalesced into one CPU notification. Only
|
| /linux/include/uapi/linux/ |
| H A D | vfio_zdev.h | 50 __u16 noi; /* Maximum number of MSIs */
|
| /linux/tools/perf/trace/beauty/arch/x86/include/asm/ |
| H A D | irq_vectors.h | 103 * Posted interrupt notification vector for all device MSIs delivered to
|
| /linux/drivers/cdx/controller/ |
| H A D | mcdi_functions.h | 114 * cdx_mcdi_msi_enable - Enable/Disable MSIs for cdx device represented
|
| /linux/drivers/parisc/ |
| H A D | iosapic.c | 30 ** to a processor write to memory or MMIO. MSIs can be generated by I/O
34 ** MSIs (e.g. GSC or HP-PB) or convert line based interrupts into MSIs
35 ** (e.g. PCI and EISA). IA64 supports MSIs via a "local SAPIC" which
|
| /linux/arch/powerpc/platforms/pasemi/ |
| H A D | msi.c | 92 * few MSIs for someone, but restrictions will apply to how the in pasemi_msi_setup_msi_irqs()
|
| /linux/drivers/net/wireless/ath/ath10k/ |
| H A D | hw.h | 847 * Granted MSIs are assigned as follows:
849 * Remaining MSIs, if any, are used by Copy Engines
856 /* MSIs for Copy Engines */
|
| /linux/arch/riscv/include/asm/ |
| H A D | kvm_aia.h | 27 /* Number of MSIs */
|
| /linux/arch/powerpc/sysdev/ |
| H A D | mpic_u3msi.c | 79 /* U4 PCIe MSIs need to write to the special register in in find_u4_magic_addr()
|