Lines Matching +full:hardware +full:- +full:based

1 # SPDX-License-Identifier: GPL-2.0
3 menu "DesignWare-based PCIe controllers"
37 core plus Annapurna Labs proprietary hardware wrappers. This is
38 required only for DT-based platforms. ACPI platforms with the
48 Versal2 SoCs. The AMD MDB Versal2 PCIe controller is based on
49 DesignWare IP and therefore the driver re-uses the DesignWare
59 SoCs. The PCI controller on Amlogic is based on DesignWare hardware
60 and therefore the driver re-uses the DesignWare core functions to
67 bool "Axis ARTPEC-6 PCIe controller (host mode)"
73 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
77 bool "Axis ARTPEC-6 PCIe controller (endpoint mode)"
83 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
87 tristate "Baikal-T1 PCIe controller"
92 Enables support for the PCIe controller in the Baikal-T1 SoC to work
93 in host mode. It's based on the Synopsys DWC PCIe v4.60a IP-core.
106 work in Root Complex mode. The PCI controller on i.MX is based
107 on DesignWare hardware and therefore the driver re-uses the
118 work in endpoint mode. The PCI controller on i.MX is based
119 on DesignWare hardware and therefore the driver re-uses the
183 The PCIe controller uses the DesignWare core plus Intel-specific
184 hardware wrappers.
198 The PCIe controller is based on DesignWare Hardware and uses
211 The PCIe controller is based on DesignWare Hardware and uses
215 bool "Marvell Armada-8K PCIe controller"
221 Armada-8K SoCs. The PCIe controller on Armada-8K is based on
222 DesignWare hardware and therefore the driver re-uses the
239 enable host-specific features PCIE_TEGRA194_HOST must be selected and
240 in order to enable device-specific features PCIE_TEGRA194_EP must be
254 enable host-specific features PCIE_TEGRA194_HOST must be selected and
255 in order to enable device-specific features PCIE_TEGRA194_EP must be
262 bool "Platform bus based DesignWare PCIe controller (host mode)"
271 host-specific features PCIE_DW_PLAT_HOST must be selected and in
272 order to enable device-specific features PCI_DW_PLAT_EP must be
276 bool "Platform bus based DesignWare PCIe controller (endpoint mode)"
286 host-specific features PCIE_DW_PLAT_HOST must be selected and in
287 order to enable device-specific features PCI_DW_PLAT_EP must be
303 PCIe controller uses the DesignWare core plus Qualcomm-specific
304 hardware wrappers.
315 plus Qualcomm-specific hardware wrappers.
321 tristate "Renesas R-Car Gen4 PCIe controller (host mode)"
327 Say Y here if you want PCIe controller (host mode) on R-Car Gen4 SoCs.
329 called pcie-rcar-gen4.ko. This uses the DesignWare core.
332 tristate "Renesas R-Car Gen4 PCIe controller (endpoint mode)"
338 Say Y here if you want PCIe controller (endpoint mode) on R-Car Gen4
340 will be called pcie-rcar-gen4.ko. This uses the DesignWare core.
374 to work in host mode. The PCI controller is based on the DesignWare
375 hardware and therefore the driver re-uses the DesignWare core
440 host-specific features PCI_DRA7XX_HOST must be selected and in order
441 to enable device-specific features PCI_DRA7XX_EP must be selected.
455 host-specific features PCI_DRA7XX_HOST must be selected and in order
456 to enable device-specific features PCI_DRA7XX_EP must be selected.
470 work in host mode. The PCI controller on Keystone is based on
471 DesignWare hardware and therefore the driver re-uses the
482 work in endpoint mode. The PCI controller on Keystone is based
483 on DesignWare hardware and therefore the driver re-uses the