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

1 # SPDX-License-Identifier: GPL-2.0
3 menu "DesignWare-based PCIe controllers"
38 	  core plus Annapurna Labs proprietary hardware wrappers. This is
39 	  required only for DT-based platforms. ACPI platforms with the
49 	  Versal2 SoCs. The AMD MDB Versal2 PCIe controller is based on
50 	  DesignWare IP and therefore the driver re-uses the DesignWare
60 	  SoCs. The PCI controller on Amlogic is based on DesignWare hardware
61 	  and therefore the driver re-uses the DesignWare core functions to
68 	bool "Axis ARTPEC-6 PCIe controller (host mode)"
74 	  Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
78 	bool "Axis ARTPEC-6 PCIe controller (endpoint mode)"
84 	  Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
88 	tristate "Baikal-T1 PCIe controller"
93 	  Enables support for the PCIe controller in the Baikal-T1 SoC to work
94 	  in host mode. It's based on the Synopsys DWC PCIe v4.60a IP-core.
107 	  work in Root Complex mode. The PCI controller on i.MX is based
108 	  on DesignWare hardware and therefore the driver re-uses the
119 	  work in endpoint mode. The PCI controller on i.MX is based
120 	  on DesignWare hardware and therefore the driver re-uses the
184 	  The PCIe controller uses the DesignWare core plus Intel-specific
185 	  hardware wrappers.
199 	  The PCIe controller is based on DesignWare Hardware and uses
212 	  The PCIe controller is based on DesignWare Hardware and uses
216 	bool "Marvell Armada-8K PCIe controller"
222 	  Armada-8K SoCs. The PCIe controller on Armada-8K is based on
223 	  DesignWare hardware and therefore the driver re-uses the
240 	  enable host-specific features PCIE_TEGRA194_HOST must be selected and
241 	  in order to enable device-specific features PCIE_TEGRA194_EP must be
255 	  enable host-specific features PCIE_TEGRA194_HOST must be selected and
256 	  in order to enable device-specific features PCIE_TEGRA194_EP must be
263 	bool "Platform bus based DesignWare PCIe controller (host mode)"
272 	  host-specific features PCIE_DW_PLAT_HOST must be selected and in
273 	  order to enable device-specific features PCI_DW_PLAT_EP must be
277 	bool "Platform bus based DesignWare PCIe controller (endpoint mode)"
287 	  host-specific features PCIE_DW_PLAT_HOST must be selected and in
288 	  order to enable device-specific features PCI_DW_PLAT_EP must be
305 	  PCIe controller uses the DesignWare core plus Qualcomm-specific
306 	  hardware wrappers.
317 	  plus Qualcomm-specific hardware wrappers.
323 	tristate "Renesas R-Car Gen4 PCIe controller (host mode)"
329 	  Say Y here if you want PCIe controller (host mode) on R-Car Gen4 SoCs.
331 	  called pcie-rcar-gen4.ko. This uses the DesignWare core.
334 	tristate "Renesas R-Car Gen4 PCIe controller (endpoint mode)"
340 	  Say Y here if you want PCIe controller (endpoint mode) on R-Car Gen4
342 	  will be called pcie-rcar-gen4.ko. This uses the DesignWare core.
376 	  to work in host mode. The PCI controller is based on the DesignWare
377 	  hardware and therefore the driver re-uses the DesignWare core
433 	  Enables Root Complex (RC) support for the DesignWare core based PCIe
437 	  will be called pcie-stm32.
445 	  Enables Endpoint (EP) support for the DesignWare core based PCIe
449 	  will be called pcie-stm32-ep.
466 	  host-specific features PCI_DRA7XX_HOST must be selected and in order
467 	  to enable device-specific features PCI_DRA7XX_EP must be selected.
481 	  host-specific features PCI_DRA7XX_HOST must be selected and in order
482 	  to enable device-specific features PCI_DRA7XX_EP must be selected.
496 	  work in host mode. The PCI controller on Keystone is based on
497 	  DesignWare hardware and therefore the driver re-uses the
508 	  work in endpoint mode. The PCI controller on Keystone is based
509 	  on DesignWare hardware and therefore the driver re-uses the