Home
last modified time | relevance | path

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

123

/linux-6.14.4/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 …]
Dnvidia,tegra194-pcie.yaml39 - description: aperture to access the configuration space through ECAM.
48 - const: ecam
338 <0x24 0x30000000 0x0 0x10000000>; /* ECAM (256MB) */
339 reg-names = "appl", "config", "atu_dma", "dbi", "ecam";
Dpcie-al.txt25 - "config" PCIe ECAM space
/linux-6.14.4/arch/x86/pci/
Dmmconfig-shared.c3 * Low-level direct PCI config space access via ECAM - common code between
29 /* Indicate if the ECAM resources have been placed into the resource table */
93 "PCI ECAM %04x [bus %02x-%02x]", segment, start, end); in pci_mmconfig_alloc()
112 pr_info("ECAM %pR (base %#lx) for domain %04x [bus %02x-%02x]\n", in pci_mmconfig_add()
207 /* ECAM is not enabled */ in pci_mmcfg_amd_fam10h()
369 pr_info("%s with ECAM support\n", name); in pci_mmcfg_check_hostbridge()
489 dev_info(dev, "ECAM %pR reserved as %s\n", in is_mmconf_reserved()
492 pr_info("ECAM %pR reserved as %s\n", &cfg->res, method); in is_mmconf_reserved()
501 "PCI ECAM %04x [bus %02x-%02x]", in is_mmconf_reserved()
505 dev_info(dev, "ECAM %pR (base %#lx) (size reduced!)\n", in is_mmconf_reserved()
[all …]
/linux-6.14.4/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()
63 { .compatible = "pci-host-ecam-generic",
66 { .compatible = "marvell,armada8k-pcie-ecam",
69 { .compatible = "socionext,synquacer-pcie-ecam",
72 { .compatible = "snps,dw-pcie-ecam",
DMakefile15 obj-$(CONFIG_PCI_HOST_THUNDER_ECAM) += pci-thunder-ecam.o
50 # pci_root.c driver but don't support standard ECAM config access.
51 # They contain MCFG quirks to replace the generic ECAM accessors with
61 obj-$(CONFIG_ARM64) += pci-thunder-ecam.o
Dpci-thunder-pem.c13 #include <linux/pci-ecam.h>
24 * Enhanced Configuration Access Mechanism (ECAM)
26 * N.B. This is a non-standard platform-specific ECAM bus shift value. For
28 * include/linux/pci-ecam.h.
Dpcie-xilinx-common.h7 #include <linux/pci-ecam.h>
DKconfig110 bool "Cavium Thunder ECAM controller to on-chip devices on pass-1.x silicon"
115 Say Y here if you want ECAM support for CN88XX-Pass-1.x Cavium Thunder SoCs.
Dpcie-xilinx-cpm.c321 _IC(CFG_TIMEOUT, "ECAM access timeout"),
333 _IC(CFG_PCIE_TIMEOUT, "PCIe ECAM access timeout"),
334 _IC(CFG_ERR_POISON, "ECAM poisoned completion received"),
Dpci-host-common.c15 #include <linux/pci-ecam.h>
/linux-6.14.4/drivers/pci/
Decam.c11 #include <linux/pci-ecam.h>
44 /* ECAM-compliant platforms need not supply ops->bus_shift */ in pci_ecam_create()
59 dev_warn(dev, "ECAM area %pR can only accommodate %pR (reduced from %pR desired)\n", in pci_ecam_create()
67 cfg->res.name = "PCI ECAM"; in pci_ecam_create()
72 dev_err(dev, "can't claim ECAM area %pR: address conflict with %s %pR\n", in pci_ecam_create()
92 dev_info(dev, "ECAM at %pR for %pR\n", &cfg->res, &cfg->busr); in pci_ecam_create()
96 dev_err(dev, "ECAM ioremap failed\n"); in pci_ecam_create()
199 /* ECAM ops */
212 /* ECAM ops for 32-bit access only (non-compliant) */
223 /* ECAM ops for 32-bit read only (non-compliant) */
DMakefile32 obj-$(CONFIG_PCI_ECAM) += ecam.o
/linux-6.14.4/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-6.14.4/include/linux/
Dpci-ecam.h18 * Enhanced Configuration Access Mechanism (ECAM)
57 * use ECAM.
69 struct device *parent;/* ECAM res was from this dev */
81 /* default ECAM ops */
98 /* for DT-based PCI controllers that support ECAM */
/linux-6.14.4/arch/loongarch/pci/
Dacpi.c11 #include <linux/pci-ecam.h>
120 cfg->res.name = "PCI ECAM"; in arch_pci_ecam_create()
125 dev_err(dev, "can't claim ECAM area %pR: address conflict with %s %pR\n", in arch_pci_ecam_create()
139 dev_info(dev, "ECAM at %pR for %pR\n", &cfg->res, &cfg->busr); in arch_pci_ecam_create()
145 dev_err(dev, "ECAM ioremap failed\n"); in arch_pci_ecam_create()
168 dev_err(dev, "%04x:%pR ECAM region not found, use default value\n", seg, bus_res); in pci_acpi_setup_ecam_mapping()
186 dev_err(dev, "%04x:%pR error %ld mapping ECAM\n", seg, bus_res, PTR_ERR(cfg)); in pci_acpi_setup_ecam_mapping()
/linux-6.14.4/drivers/pci/controller/dwc/
Dpcie-hisi.c16 #include <linux/pci-ecam.h>
159 .compatible = "hisilicon,hip06-pcie-ecam",
163 .compatible = "hisilicon,hip07-pcie-ecam",
172 .name = "hisi-pcie-almost-ecam",
DMakefile33 # pci_root.c driver but don't support standard ECAM config access.
34 # They contain MCFG quirks to replace the generic ECAM accessors with
Dpcie-al.c12 #include <linux/pci-ecam.h>
267 dev_warn(pcie->dev, "ECAM window size is larger than 256MB. Cutting off at 256\n"); in al_pcie_config_prepare()
/linux-6.14.4/Documentation/translations/zh_CN/PCI/
Dacpi-info.rst60 ECAM，尽管对[6]的严格解释可能禁止这样做。旧的x86和ia64内核假定所有的地址空间描述
69 型配置访问方法（ECAM）。主桥消耗ECAM内存地址空间并将内存访问转换为PCI配置访问。该规范
/linux-6.14.4/drivers/pci/controller/plda/
Dpcie-microchip-host.c21 #include <linux/pci-ecam.h>
298 static void mc_pcie_enable_msi(struct mc_pcie *port, void __iomem *ecam) in mc_pcie_enable_msi() argument
305 reg = readw_relaxed(ecam + MC_MSI_CAP_CTRL_OFFSET + PCI_MSI_FLAGS); in mc_pcie_enable_msi()
307 writew_relaxed(reg, ecam + MC_MSI_CAP_CTRL_OFFSET + PCI_MSI_FLAGS); in mc_pcie_enable_msi()
312 writew_relaxed(reg, ecam + MC_MSI_CAP_CTRL_OFFSET + PCI_MSI_FLAGS); in mc_pcie_enable_msi()
316 ecam + MC_MSI_CAP_CTRL_OFFSET + PCI_MSI_ADDRESS_LO); in mc_pcie_enable_msi()
318 ecam + MC_MSI_CAP_CTRL_OFFSET + PCI_MSI_ADDRESS_HI); in mc_pcie_enable_msi()
/linux-6.14.4/arch/arm64/boot/dts/cavium/
Dthunder2-99xx.dtsi98 compatible = "pci-host-ecam-generic";
104 /* ECAM at 0x3000_0000 - 0x4000_0000 */
/linux-6.14.4/drivers/acpi/
Dpci_mcfg.c14 #include <linux/pci-ecam.h>
234 dev_info(&root->device->dev, "MCFG quirk: ECAM at %pR for %pR with %ps\n", in pci_mcfg_apply_quirks()
278 * Allow quirks to override default ECAM ops and CFG resource in pci_mcfg_lookup()
/linux-6.14.4/arch/xtensa/boot/dts/
Dvirt.dts49 compatible = "pci-host-ecam-generic";
/linux-6.14.4/Documentation/devicetree/bindings/net/
Dnxp,netc-blk-ctrl.yaml87 compatible = "pci-host-ecam-generic";

123