From: Francesco Lavra <flavra@baylibre.com>
To: "Jon Hunter" <jonathanh@nvidia.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
thierry.reding@gmail.com,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Mayank Rana" <mayank.rana@oss.qualcomm.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Shradha Todi" <shradha.t@samsung.com>,
"Thippeswamy Havalige" <thippeswamy.havalige@amd.com>,
"Inochi Amaoto" <inochiama@gmail.com>,
"Vidya Sagar" <vidyas@nvidia.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"linux-tegra @ vger . kernel . org" <linux-tegra@vger.kernel.org>
Subject: [PATCH v2] PCI: tegra194: allow enabling driver on Tegra234
Date: Fri, 2 Jan 2026 20:09:21 +0100 [thread overview]
Message-ID: <20260102190921.3765226-1-flavra@baylibre.com> (raw)
This driver runs (for both host and endpoint operation) also on Tegra234.
To allow enabling this driver on Tegra234, add a Kconfig dependency on
ARCH_TEGRA_234_SOC; in addition, amend the Kconfig help text to reflect the
fact that this driver is no longer exclusive to Tegra194.
Signed-off-by: Francesco Lavra <flavra@baylibre.com>
---
Changes from v1 [1]:
- added ARCH_TEGRA_234_SOC instead of replacing ARCH_TEGRA_194_SOC with
ARCH_TEGRA (Jon)
[1] https://lore.kernel.org/linux-pci/20251126102530.4110067-1-flavra@baylibre.com/T/
drivers/pci/controller/dwc/Kconfig | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/drivers/pci/controller/dwc/Kconfig b/drivers/pci/controller/dwc/Kconfig
index 519b59422b47..cb8a9c049158 100644
--- a/drivers/pci/controller/dwc/Kconfig
+++ b/drivers/pci/controller/dwc/Kconfig
@@ -228,33 +228,33 @@ config PCIE_TEGRA194
config PCIE_TEGRA194_HOST
tristate "NVIDIA Tegra194 (and later) PCIe controller (host mode)"
- depends on ARCH_TEGRA_194_SOC || COMPILE_TEST
+ depends on ARCH_TEGRA_194_SOC || ARCH_TEGRA_234_SOC || COMPILE_TEST
depends on PCI_MSI
select PCIE_DW_HOST
select PHY_TEGRA194_P2U
select PCIE_TEGRA194
help
- Enables support for the PCIe controller in the NVIDIA Tegra194 SoC to
- work in host mode. There are two instances of PCIe controllers in
- Tegra194. This controller can work either as EP or RC. In order to
- enable host-specific features PCIE_TEGRA194_HOST must be selected and
- in order to enable device-specific features PCIE_TEGRA194_EP must be
- selected. This uses the DesignWare core.
+ Enables support for the PCIe controller in the NVIDIA Tegra194 and
+ later SoCs to work in host mode. This controller can work either as
+ EP or RC. In order to enable host-specific features
+ PCIE_TEGRA194_HOST must be selected and in order to enable
+ device-specific features PCIE_TEGRA194_EP must be selected. This uses
+ the DesignWare core.
config PCIE_TEGRA194_EP
tristate "NVIDIA Tegra194 (and later) PCIe controller (endpoint mode)"
- depends on ARCH_TEGRA_194_SOC || COMPILE_TEST
+ depends on ARCH_TEGRA_194_SOC || ARCH_TEGRA_234_SOC || COMPILE_TEST
depends on PCI_ENDPOINT
select PCIE_DW_EP
select PHY_TEGRA194_P2U
select PCIE_TEGRA194
help
- Enables support for the PCIe controller in the NVIDIA Tegra194 SoC to
- work in endpoint mode. There are two instances of PCIe controllers in
- Tegra194. This controller can work either as EP or RC. In order to
- enable host-specific features PCIE_TEGRA194_HOST must be selected and
- in order to enable device-specific features PCIE_TEGRA194_EP must be
- selected. This uses the DesignWare core.
+ Enables support for the PCIe controller in the NVIDIA Tegra194 and
+ later SoCs to work in endpoint mode. This controller can work either
+ as EP or RC. In order to enable host-specific features
+ PCIE_TEGRA194_HOST must be selected and in order to enable
+ device-specific features PCIE_TEGRA194_EP must be selected. This uses
+ the DesignWare core.
config PCIE_NXP_S32G
bool "NXP S32G PCIe controller (host mode)"
--
2.39.5
next reply other threads:[~2026-01-02 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 19:09 Francesco Lavra [this message]
2026-01-05 11:53 ` Jon Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260102190921.3765226-1-flavra@baylibre.com \
--to=flavra@baylibre.com \
--cc=bhelgaas@google.com \
--cc=inochiama@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mayank.rana@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=shradha.t@samsung.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=thippeswamy.havalige@amd.com \
--cc=vidyas@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®