/freebsd/sys/contrib/device-tree/Bindings/pci/ |
H A 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 23 Documentation/devicetree/bindings/interrupt-controller/msi.txt. 30 ------------------- 32 - msi-map: Maps a Requester ID to an MSI controller and associated 33 msi-specifier data. The property is an arbitrary number of tuples of 34 (rid-base,msi-controller,msi-base,length), where: 36 * rid-base is a single cell describing the first RID matched by the entry. 38 * msi-controller is a single phandle to an MSI controller [all …]
|
H A D | brcm,iproc-pcie.txt | 1 * Broadcom iProc PCIe controller with the platform bus interface 4 - compatible: 5 "brcm,iproc-pcie" for the first generation of PAXB based controller, 7 "brcm,iproc-pcie-paxb-v2" for the second generation of PAXB-based 9 "brcm,iproc-pcie-paxc" for the first generation of PAXC based 10 controller, used in NS2 11 "brcm,iproc-pcie-paxc-v2" for the second generation of PAXC based 12 controller, used in Stingray 13 PAXB-based root complex is used for external endpoint devices. PAXC-based 15 - reg: base address and length of the PCIe controller I/O register space [all …]
|
H A D | xgene-pci-msi.txt | 1 * AppliedMicro X-Gene v1 PCIe MSI controller 5 - compatible: should be "apm,xgene1-msi" to identify 6 X-Gene v1 PCIe MSI controller block. 7 - msi-controller: indicates that this is an X-Gene v1 PCIe MSI controller node 8 - reg: physical base address (0x79000000) and length (0x900000) for controller 9 registers. These registers include the MSI termination address and data 10 registers as well as the MSI interrupt status registers. 11 - reg-names: not required 12 - interrupts: A list of 16 interrupt outputs of the controller, starting from 14 - interrupt-names: not required [all …]
|
H A D | altr,msi-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/altr,msi-controller.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: Altera PCIe MSI controller 11 - Matthew Gerlach <matthew.gerlach@linux.intel.com> 16 - altr,msi-1.0 20 - description: CSR registers 21 - description: Vectors slave port region 23 reg-names: [all …]
|
H A D | brcm,iproc-pcie.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pci/brcm,iproc-pcie.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Broadcom iProc PCIe controller with the platform bus interface 10 - Ray Jui <ray.jui@broadcom.com> 11 - Scott Branden <scott.branden@broadcom.com> 14 - $ref: /schemas/pci/pci-host-bridge.yaml# 19 - enum: 20 # for the first generation of PAXB based controller, used in SoCs [all …]
|
H A D | altera-pcie-msi.txt | 1 * Altera PCIe MSI controller 4 - compatible: should contain "altr,msi-1.0" 5 - reg: specifies the physical base address of the controller and 7 - reg-names: must include the following entries: 10 - interrupts: specifies the interrupt source of the parent interrupt 11 controller. The format of the interrupt specifier depends on the 12 parent interrupt controller. 13 - num-vectors: number of vectors, range 1 to 32. 14 - msi-controller: indicates that this is MSI controller node 18 msi0: msi@0xFF200000 { [all …]
|
H A D | plda,xpressrich3-axi-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pci/plda,xpressrich3-axi-common.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Daire McNamara <daire.mcnamara@microchip.com> 11 - Kevin Xie <kevin.xie@starfivetech.com> 17 - $ref: /schemas/pci/pci-host-bridge.yaml# 23 reg-names: 25 - const: cfg 26 - const: apb [all …]
|
H A D | brcm,stb-pcie.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pci/brcm,stb-pcie.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Brcmstb PCIe Host Controller 10 - Jim Quinlan <james.quinlan@broadcom.com> 15 - enum: 16 - brcm,bcm2711-pcie # The Raspberry Pi 4 17 - brcm,bcm4908-pcie 18 - brcm,bcm7211-pcie # Broadcom STB version of RPi4 [all …]
|
H A D | layerscape-pcie-gen4.txt | 1 NXP Layerscape PCIe Gen4 controller 3 This PCIe controller is based on the Mobiveil PCIe IP and thus inherits all 4 the common properties defined in mobiveil-pcie.txt. 7 - compatible: should contain the platform identifier such as: 8 "fsl,lx2160a-pcie" 9 - reg: base addresses and lengths of the PCIe controller register blocks. 11 "config_axi_slave": PCIe controller registers 12 - interrupts: A list of interrupt outputs of the controller. Must contain an 13 entry for each entry in the interrupt-names property. 14 - interrupt-names: It could include the following entries: [all …]
|
H A D | aardvark-pci.txt | 1 Aardvark PCIe controller 3 This PCIe controller is used on the Marvell Armada 3700 ARM64 SoC. 5 The Device Tree node describing an Aardvark PCIe controller must 8 - compatible: Should be "marvell,armada-3700-pcie" 9 - reg: range of registers for the PCIe controller 10 - interrupts: the interrupt line of the PCIe controller 11 - #address-cells: set to <3> 12 - #size-cells: set to <2> 13 - device_type: set to "pci" 14 - ranges: ranges for the PCI memory and I/O regions [all …]
|
H A D | xlnx,nwl-pcie.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pci/xlnx,nwl-pcie.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Thippeswamy Havalige <thippeswamy.havalige@amd.com> 13 - $ref: /schemas/pci/pci-host-bridge.yaml# 14 - $ref: /schemas/interrupt-controller/msi-controller.yaml# 18 const: xlnx,nwl-pcie-2.11 22 - description: PCIe bridge registers location. 23 - description: PCIe Controller registers location. [all …]
|
H A D | apple,pcie.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Apple PCIe host controller 10 - Mark Kettenis <kettenis@openbsd.org> 13 The Apple PCIe host controller is a PCIe host controller with 16 The controller incorporates Synopsys DesigWare PCIe logic to 22 the standard "reset-gpios" and "max-link-speed" properties appear on 26 MSIs are handled by the PCIe controller and translated into regular 29 the PCIe controller's port registers. [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/interrupt-controller/ |
H A 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, 14 - The doorbell (the MMIO address written to). 17 they can address. An MSI controller may feature a number of doorbells. 19 - The payload (the value written to the doorbell). 22 MSI controllers may have restrictions on permitted payloads. 24 - Sideband information accompanying the write. 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 [all …]
|
H A D | fsl,ls-msi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/fsl,ls-msi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Freescale Layerscape SCFG PCIe MSI controller 10 This interrupt controller hardware is a second level interrupt controller that 11 is hooked to a parent interrupt controller: e.g: ARM GIC for ARM-based 12 platforms. If interrupt-parent is not provided, the default parent interrupt 13 controller will be used. 15 Each PCIe node needs to have property msi-parent that points to [all …]
|
H A D | fsl,ls-scfg-msi.txt | 1 * Freescale Layerscape SCFG PCIe MSI controller 5 - compatible: should be "fsl,<soc-name>-msi" to identify 6 Layerscape PCIe MSI controller block such as: 7 "fsl,ls1021a-msi" 8 "fsl,ls1043a-msi" 9 "fsl,ls1046a-msi" 10 "fsl,ls1043a-v1.1-msi" 11 "fsl,ls1012a-msi" 12 - msi-controller: indicates that this is a PCIe MSI controller node 13 - reg: physical base address of the controller and length of memory mapped. [all …]
|
H A D | fsl,mu-msi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/fsl,mu-msi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Freescale/NXP i.MX Messaging Unit (MU) work as msi controller 10 - Frank Li <Frank.Li@nxp.com> 23 registers (Processor A-side, Processor B-side). 25 MU can work as msi interrupt controller to do doorbell 28 - $ref: /schemas/interrupt-controller/msi-controller.yaml# 33 - fsl,imx6sx-mu-msi [all …]
|
H A D | loongson,pch-msi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/loongson,pch-msi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Loongson PCH MSI Controller 10 - Jiaxun Yang <jiaxun.yang@flygoat.com> 13 This interrupt controller is found in the Loongson LS7A family of PCH for 14 transforming interrupts from PCIe MSI into HyperTransport vectorized 19 const: loongson,pch-msi-1.0 24 loongson,msi-base-vec: [all …]
|
H A D | msi-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/msi-controller.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: MSI controller 10 - Marc Zyngier <maz@kernel.org> 13 An MSI controller signals interrupts to a CPU when a write is made 14 to an MMIO address by some master. An MSI controller may feature a 18 "#msi-cells": 20 The number of cells in an msi-specifier, required if not zero. [all …]
|
H A D | arm,gic-v3.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/arm,gic-v3.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: ARM Generic Interrupt Controller, version 3 10 - Marc Zyngier <maz@kernel.org> 15 Software Generated Interrupts (SGI), and Locality-specific Peripheral 19 - $ref: /schemas/interrupt-controller.yaml# 24 - items: 25 - enum: [all …]
|
H A D | riscv,imsics.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/riscv,imsics.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: RISC-V Incoming MSI Controller (IMSIC) 10 - Anup Patel <anup@brainfault.org> 13 The RISC-V advanced interrupt architecture (AIA) defines a per-CPU incoming 14 MSI controller (IMSIC) for handling MSIs in a RISC-V platform. The RISC-V 15 AIA specification can be found at https://github.com/riscv/riscv-aia. 17 The IMSIC is a per-CPU (or per-HART) device with separate interrupt file [all …]
|
H A D | al,alpine-msix.txt | 1 Alpine MSIX controller 3 See arm,gic-v3.txt for SPI and MSI definitions. 7 - compatible: should be "al,alpine-msix" 8 - reg: physical base address and size of the registers 9 - interrupt-controller: identifies the node as an interrupt controller 10 - msi-controller: identifies the node as an PCI Message Signaled Interrupt 11 controller 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 18 compatible = "al,alpine-msix"; [all …]
|
H A D | arm,gic.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/arm,gic.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: ARM Generic Interrupt Controller v1 and v2 10 - Marc Zyngier <marc.zyngier@arm.com> 18 Secondary GICs are cascaded into the upward interrupt controller and do not 22 - $ref: /schemas/interrupt-controller.yaml# 27 - items: 28 - enum: [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/bus/ |
H A D | fsl,imx8qxp-pixel-link-msi-bus.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/bus/fsl,imx8qxp-pixe [all...] |
/freebsd/sys/contrib/device-tree/src/arm64/marvell/ |
H A D | armada-ap80x.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 8 #include <dt-bindings/interrupt-controller/arm-gic.h> 9 #include <dt-bindings/thermal/thermal.h> 11 /dts-v1/; 14 #address-cells = <2>; 15 #size-cells = <2>; 25 compatible = "arm,psci-0.2"; 29 reserved-memory { 30 #address-cells = <2>; 31 #size-cells = <2>; [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/misc/ |
H A D | fsl,qoriq-mc.txt | 3 The Freescale Management Complex (fsl-mc) is a hardware resource 5 network-oriented packet processing applications. After the fsl-mc 12 For an overview of the DPAA2 architecture and fsl-mc bus see: 16 same hardware "isolation context" and a 10-bit value called an ICID 21 between ICIDs and IOMMUs, so an iommu-map property is used to define 28 For arm-smmu binding, see: 31 The MSI writes are accompanied by sideband data which is derived from the ICID. 32 The msi-map property is used to associate the devices with both the ITS 33 controller and the sideband data which accompanies the writes. 35 For generic MSI bindings, see [all …]
|