Lines Matching +full:versal2 +full:- +full:mdb +full:- +full:host
1 # SPDX-License-Identifier: GPL-2.0
3 menu "DesignWare-based PCIe controllers"
37 required only for DT-based platforms. ACPI platforms with the
41 bool "AMD MDB Versal2 PCIe controller"
47 Versal2 SoCs. The AMD MDB Versal2 PCIe controller is based on
48 DesignWare IP and therefore the driver re-uses the DesignWare
59 and therefore the driver re-uses the DesignWare core functions to
66 bool "Axis ARTPEC-6 PCIe controller (host mode)"
72 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
73 host mode. This uses the DesignWare core.
76 bool "Axis ARTPEC-6 PCIe controller (endpoint mode)"
82 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
86 tristate "Baikal-T1 PCIe controller"
91 Enables support for the PCIe controller in the Baikal-T1 SoC to work
92 in host mode. It's based on the Synopsys DWC PCIe v4.60a IP-core.
98 bool "Freescale i.MX6/7/8 PCIe controller (host mode)"
106 on DesignWare hardware and therefore the driver re-uses the
118 on DesignWare hardware and therefore the driver re-uses the
122 bool "Freescale Layerscape PCIe controller (host mode)"
129 SoCs to work in Host mode.
180 Say 'Y' here to enable PCIe Host controller support on Intel
182 The PCIe controller uses the DesignWare core plus Intel-specific
189 bool "Intel Keem Bay PCIe controller (host mode)"
196 to work in host mode.
214 bool "Marvell Armada-8K PCIe controller"
220 Armada-8K SoCs. The PCIe controller on Armada-8K is based on
221 DesignWare hardware and therefore the driver re-uses the
228 tristate "NVIDIA Tegra194 (and later) PCIe controller (host mode)"
236 work in host mode. There are two instances of PCIe controllers in
238 enable host-specific features PCIE_TEGRA194_HOST must be selected and
239 in order to enable device-specific features PCIE_TEGRA194_EP must be
253 enable host-specific features PCIE_TEGRA194_HOST must be selected and
254 in order to enable device-specific features PCIE_TEGRA194_EP must be
261 bool "Platform bus based DesignWare PCIe controller (host mode)"
267 work in host mode. There are two instances of PCIe controller in
270 host-specific features PCIE_DW_PLAT_HOST must be selected and in
271 order to enable device-specific features PCI_DW_PLAT_EP must be
285 host-specific features PCIE_DW_PLAT_HOST must be selected and in
286 order to enable device-specific features PCI_DW_PLAT_EP must be
293 bool "Qualcomm PCIe controller (host mode)"
301 PCIe controller uses the DesignWare core plus Qualcomm-specific
313 plus Qualcomm-specific hardware wrappers.
319 tristate "Renesas R-Car Gen4 PCIe controller (host mode)"
325 Say Y here if you want PCIe controller (host mode) on R-Car Gen4 SoCs.
327 called pcie-rcar-gen4.ko. This uses the DesignWare core.
330 tristate "Renesas R-Car Gen4 PCIe controller (endpoint mode)"
336 Say Y here if you want PCIe controller (endpoint mode) on R-Car Gen4
338 will be called pcie-rcar-gen4.ko. This uses the DesignWare core.
344 bool "Rockchip DesignWare PCIe controller (host mode)"
352 Rockchip SoC (except RK3399) to work in host mode.
372 to work in host mode. The PCI controller is based on the DesignWare
373 hardware and therefore the driver re-uses the DesignWare core
386 bool "Socionext UniPhier PCIe controller (host mode)"
392 Say Y here if you want PCIe host controller support on UniPhier SoCs.
417 tristate "TI DRA7xx PCIe controller (host mode)"
426 host mode. There are two instances of PCIe controller in DRA7xx.
428 host-specific features PCI_DRA7XX_HOST must be selected and in order
429 to enable device-specific features PCI_DRA7XX_EP must be selected.
443 host-specific features PCI_DRA7XX_HOST must be selected and in order
444 to enable device-specific features PCI_DRA7XX_EP must be selected.
451 bool "TI Keystone PCIe controller (host mode)"
458 work in host mode. The PCI controller on Keystone is based on
459 DesignWare hardware and therefore the driver re-uses the
471 on DesignWare hardware and therefore the driver re-uses the