Lines Matching +full:pci +full:- +full:ep
1 # SPDX-License-Identifier: GPL-2.0
3 menu "DesignWare-based PCIe controllers"
4 depends on PCI
27 required only for DT-based platforms. ACPI platforms with the
36 Say Y here if you want to enable PCI controller support on Amlogic
37 SoCs. The PCI controller on Amlogic is based on DesignWare hardware
38 and therefore the driver re-uses the DesignWare core functions to
45 bool "Axis ARTPEC-6 PCIe controller (host mode)"
51 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
55 bool "Axis ARTPEC-6 PCIe controller (endpoint mode)"
61 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
65 tristate "Baikal-T1 PCIe controller"
70 Enables support for the PCIe controller in the Baikal-T1 SoC to work
71 in host mode. It's based on the Synopsys DWC PCIe v4.60a IP-core.
84 work in Root Complex mode. The PCI controller on i.MX is based
85 on DesignWare hardware and therefore the driver re-uses the
96 work in endpoint mode. The PCI controller on i.MX is based
97 on DesignWare hardware and therefore the driver re-uses the
109 This controller can work either as EP or RC. The RCW[HOST_AGT_PEX]
110 determines which PCIe controller works in EP mode and which PCIe
121 This controller can work either as EP or RC. The RCW[HOST_AGT_PEX]
122 determines which PCIe controller works in EP mode and which PCIe
161 The PCIe controller uses the DesignWare core plus Intel-specific
193 bool "Marvell Armada-8K PCIe controller"
199 Armada-8K SoCs. The PCIe controller on Armada-8K is based on
200 DesignWare hardware and therefore the driver re-uses the
216 Tegra194. This controller can work either as EP or RC. In order to
217 enable host-specific features PCIE_TEGRA194_HOST must be selected and
218 in order to enable device-specific features PCIE_TEGRA194_EP must be
231 Tegra194. This controller can work either as EP or RC. In order to
232 enable host-specific features PCIE_TEGRA194_HOST must be selected and
233 in order to enable device-specific features PCIE_TEGRA194_EP must be
248 This controller can work either as EP or RC. In order to enable
249 host-specific features PCIE_DW_PLAT_HOST must be selected and in
250 order to enable device-specific features PCI_DW_PLAT_EP must be
255 depends on PCI && PCI_MSI
263 This controller can work either as EP or RC. In order to enable
264 host-specific features PCIE_DW_PLAT_HOST must be selected and in
265 order to enable device-specific features PCI_DW_PLAT_EP must be
280 PCIe controller uses the DesignWare core plus Qualcomm-specific
292 plus Qualcomm-specific hardware wrappers.
298 tristate "Renesas R-Car Gen4 PCIe controller (host mode)"
304 Say Y here if you want PCIe controller (host mode) on R-Car Gen4 SoCs.
306 called pcie-rcar-gen4.ko. This uses the DesignWare core.
309 tristate "Renesas R-Car Gen4 PCIe controller (endpoint mode)"
315 Say Y here if you want PCIe controller (endpoint mode) on R-Car Gen4
317 will be called pcie-rcar-gen4.ko. This uses the DesignWare core.
351 to work in host mode. The PCI controller is based on the DesignWare
352 hardware and therefore the driver re-uses the DesignWare core
406 This controller can work either as EP or RC. In order to enable
407 host-specific features PCI_DRA7XX_HOST must be selected and in order
408 to enable device-specific features PCI_DRA7XX_EP must be selected.
421 This controller can work either as EP or RC. In order to enable
422 host-specific features PCI_DRA7XX_HOST must be selected and in order
423 to enable device-specific features PCI_DRA7XX_EP must be selected.
437 work in host mode. The PCI controller on Keystone is based on
438 DesignWare hardware and therefore the driver re-uses the
449 work in endpoint mode. The PCI controller on Keystone is based
450 on DesignWare hardware and therefore the driver re-uses the