Home
last modified time | relevance | path

Searched full:ecam (Results 1 – 25 of 39) sorted by relevance

12

/linux-5.10/Documentation/devicetree/bindings/pci/
Dhost-generic-pci.yaml31 While ECAM extends this by 4 bits to accommodate 4k of function space:
38 description: Depends on the layout of configuration space (CAM vs ECAM
46 - const: pci-host-ecam-generic
51 some Cavium ThunderX processors. These devices have ECAM-based config
55 const: cavium,pci-host-thunder-ecam
60 HiSilicon Hip06/Hip07 PCIe host bridge in almost-ECAM mode. Some
61 firmware places the host controller in a mode where it is ECAM
64 - hisilicon,hip06-pcie-ecam
65 - hisilicon,hip07-pcie-ecam
69 that cover all config, MMIO and I/O spaces in a [mostly] ECAM
[all …]
Dpcie-al.txt25 - "config" PCIe ECAM space
Dpci.txt77 compatible = "pci-host-ecam-generic";
/linux-5.10/drivers/pci/
Decam.c11 #include <linux/pci-ecam.h>
53 dev_warn(dev, "ECAM area %pR can only accommodate %pR (reduced from %pR desired)\n", in pci_ecam_create()
61 cfg->res.name = "PCI ECAM"; in pci_ecam_create()
66 dev_err(dev, "can't claim ECAM area %pR: address conflict with %s %pR\n", in pci_ecam_create()
93 dev_info(dev, "ECAM at %pR for %pR\n", &cfg->res, &cfg->busr); in pci_ecam_create()
97 dev_err(dev, "ECAM ioremap failed\n"); in pci_ecam_create()
150 /* ECAM ops */
162 /* ECAM ops for 32-bit access only (non-compliant) */
172 /* ECAM ops for 32-bit read only (non-compliant) */
DMakefile30 obj-$(CONFIG_PCI_ECAM) += ecam.o
/linux-5.10/drivers/pci/controller/
Dpci-host-generic.c14 #include <linux/pci-ecam.h>
31 * The Synopsys DesignWare PCIe controller in ECAM mode will not filter in pci_dw_valid_device()
64 { .compatible = "pci-host-ecam-generic",
67 { .compatible = "marvell,armada8k-pcie-ecam",
70 { .compatible = "socionext,synquacer-pcie-ecam",
73 { .compatible = "snps,dw-pcie-ecam",
DMakefile41 # pci_root.c driver but don't support standard ECAM config access.
42 # They contain MCFG quirks to replace the generic ECAM accessors with
51 obj-$(CONFIG_ARM64) += pci-thunder-ecam.o
Dpcie-xilinx-cpm.c22 #include <linux/pci-ecam.h>
309 _IC(CFG_TIMEOUT, "ECAM access timeout"),
321 _IC(CFG_PCIE_TIMEOUT, "PCIe ECAM access timeout"),
322 _IC(CFG_ERR_POISON, "ECAM poisoned completion received"),
DKconfig201 bool "Cavium Thunder ECAM controller to on-chip devices on pass-1.x silicon"
206 Say Y here if you want ECAM support for CN88XX-Pass-1.x Cavium Thunder SoCs.
Dpci-host-common.c15 #include <linux/pci-ecam.h>
Dpci-thunder-ecam.c11 #include <linux/pci-ecam.h>
361 .compatible = "cavium,pci-host-thunder-ecam",
Dpcie-xilinx.c89 /* ECAM definitions */
412 dev_warn(dev, "ECAM access timeout\n"); in xilinx_pcie_intr_handler()
/linux-5.10/Documentation/PCI/
Dacpi-info.rst52 the device-specific details.  The host bridge registers also include ECAM
66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
67 With the exception of ECAM, the bridge register space is device-specific
72 descriptors in the PNP0A03 device for bridge registers, including ECAM,
84 The PCIe spec requires the Enhanced Configuration Access Method (ECAM)
86 ia64 SAL interface [7]. A host bridge consumes ECAM memory address space
88 defines the ECAM address space layout and functionality; only the base of
92 The MCFG table must describe the ECAM space of non-hot pluggable host
94 a _CBA method in the PNP0A03 device describes the ECAM space of a
167 access to the Configuration Space, the ECAM is required as defined in
/linux-5.10/include/linux/
Dpci-ecam.h26 * use ECAM.
37 struct device *parent;/* ECAM res was from this dev */
49 /* default ECAM ops */
64 /* for DT-based PCI controllers that support ECAM */
/linux-5.10/arch/arm64/kernel/
Dpci.c18 #include <linux/pci-ecam.h>
128 dev_err(dev, "%04x:%pR ECAM region not found\n", seg, bus_res); in pci_acpi_setup_ecam_mapping()
134 dev_info(dev, "ECAM area %pR reserved by %s\n", &cfgres, in pci_acpi_setup_ecam_mapping()
137 dev_warn(dev, FW_BUG "ECAM area %pR not reserved in ACPI namespace\n", in pci_acpi_setup_ecam_mapping()
142 dev_err(dev, "%04x:%pR error %ld mapping ECAM\n", seg, bus_res, in pci_acpi_setup_ecam_mapping()
/linux-5.10/drivers/pci/controller/dwc/
Dpcie-hisi.c16 #include <linux/pci-ecam.h>
149 .compatible = "hisilicon,hip06-pcie-ecam",
153 .compatible = "hisilicon,hip07-pcie-ecam",
162 .name = "hisi-pcie-almost-ecam",
DMakefile25 # pci_root.c driver but don't support standard ECAM config access.
26 # They contain MCFG quirks to replace the generic ECAM accessors with
Dpcie-al.c12 #include <linux/pci-ecam.h>
269 dev_warn(pcie->dev, "ECAM window size is larger than 256MB. Cutting off at 256\n"); in al_pcie_config_prepare()
/linux-5.10/arch/arm64/boot/dts/cavium/
Dthunder2-99xx.dtsi98 compatible = "pci-host-ecam-generic";
104 /* ECAM at 0x3000_0000 - 0x4000_0000 */
106 reg-names = "PCI ECAM";
/linux-5.10/Documentation/devicetree/bindings/virtio/
Diommu.txt31 compatible = "pci-host-ecam-generic";
50 compatible = "pci-host-ecam-generic";
/linux-5.10/drivers/acpi/
Dpci_mcfg.c14 #include <linux/pci-ecam.h>
202 dev_info(&root->device->dev, "MCFG quirk: ECAM at %pR for %pR with %ps\n", in pci_mcfg_apply_quirks()
246 * Allow quirks to override default ECAM ops and CFG resource in pci_mcfg_lookup()
/linux-5.10/arch/xtensa/boot/dts/
Dvirt.dts49 compatible = "pci-host-ecam-generic";
/linux-5.10/arch/mips/boot/dts/loongson/
Dloongson64v_4core_virtio.dts69 compatible = "pci-host-ecam-generic";
/linux-5.10/arch/arm/boot/dts/
Dalpine.dtsi149 compatible = "pci-host-ecam-generic";
/linux-5.10/arch/arm64/boot/dts/amazon/
Dalpine-v2.dtsi129 compatible = "pci-host-ecam-generic";

12