Lines Matching full:in

71 	  which operate in Root Complex mode. The Andes QiLai SoC PCIe
85 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
95 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
105 The PCIe controller in ESWIN SoCs is based on DesignWare hardware, and
106 works only in host mode.
119 Enables support for the PCIe controller in the i.MX SoCs to
120 work in Root Complex mode. The PCI controller on i.MX is based
131 Enables support for the PCIe controller in the i.MX SoCs to
132 work in endpoint mode. The PCI controller on i.MX is based
144 SoCs to work in Host mode.
146 determines which PCIe controller works in EP mode and which PCIe
147 controller works in RC mode.
156 SoCs to work in Endpoint mode.
158 determines which PCIe controller works in EP mode and which PCIe
159 controller works in RC mode.
210 Say 'Y' here to enable support for the PCIe controller in Keem Bay
211 to work in host mode.
223 Say 'Y' here to enable support for the PCIe controller in Keem Bay
224 to work in endpoint mode.
250 Enables support for the PCIe controller in the NVIDIA Tegra194 SoC to
251 work in host mode. There are two instances of PCIe controllers in
252 Tegra194. This controller can work either as EP or RC. In order to
254 in order to enable device-specific features PCIE_TEGRA194_EP must be
265 Enables support for the PCIe controller in the NVIDIA Tegra194 SoC to
266 work in endpoint mode. There are two instances of PCIe controllers in
267 Tegra194. This controller can work either as EP or RC. In order to
269 in order to enable device-specific features PCIE_TEGRA194_EP must be
277 Enable support for the PCIe controller in NXP S32G based boards to
278 work in Host mode. The controller is based on DesignWare IP and
279 can work either as RC or EP. In order to enable host-specific
291 Enables support for the PCIe controller in the Designware IP to
292 work in host mode. There are two instances of PCIe controller in
294 This controller can work either as EP or RC. In order to enable
295 host-specific features PCIE_DW_PLAT_HOST must be selected and in
306 Enables support for the PCIe controller in the Designware IP to
307 work in endpoint mode. There are two instances of PCIe controller
308 in Designware IP.
309 This controller can work either as EP or RC. In order to enable
310 host-specific features PCIE_DW_PLAT_HOST must be selected and in
339 to work in endpoint mode. The PCIe controller uses the DesignWare core
378 Enables support for the DesignWare PCIe controller in the
379 Rockchip SoC (except RK3399) to work in host mode.
389 Enables support for the DesignWare PCIe controller in the
390 Rockchip SoC (except RK3399) to work in endpoint mode.
398 Enables support for the PCIe controller in the Samsung Exynos SoCs
399 to work in host mode. The PCI controller is based on the DesignWare
450 Enables support for the DesignWare based PCIe controller in
451 the SpacemiT K1 SoC operating in host mode. Three controllers
470 controller found in STM32MP25 SoC.
482 controller found in STM32MP25 SoC.
499 Enables support for the PCIe controller in the DRA7xx SoC to work in
500 host mode. There are two instances of PCIe controller in DRA7xx.
501 This controller can work either as EP or RC. In order to enable
502 host-specific features PCI_DRA7XX_HOST must be selected and in order
514 Enables support for the PCIe controller in the DRA7xx SoC to work in
515 endpoint mode. There are two instances of PCIe controller in DRA7xx.
516 This controller can work either as EP or RC. In order to enable
517 host-specific features PCI_DRA7XX_HOST must be selected and in order
537 Enables support for the PCIe controller in the Keystone SoC to
538 work in host mode. The PCI controller on Keystone is based on
550 Enables support for the PCIe controller in the Keystone SoC to
551 work in endpoint mode. The PCI controller on Keystone is based
571 Enables support for the PCIe controller in the UltraRISC SoC.