From: Aksh Garg <a-garg7@ti.com>
To: <linux-pci@vger.kernel.org>, <lpieralisi@kernel.org>,
<kwilczynski@kernel.org>, <mani@kernel.org>, <robh@kernel.org>,
<bhelgaas@google.com>, <s-vadapalli@ti.com>, <arnd@arndb.de>,
<mpillai@cadence.com>, <hans.zhang@cixtech.com>,
<unicorn_wang@outlook.com>, <kishon@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <danishanwar@ti.com>, <a-garg7@ti.com>
Subject: [PATCH] PCI: cadence: j721e: Add support for PCI NTB functionality
Date: Fri, 20 Feb 2026 15:40:30 +0530 [thread overview]
Message-ID: <20260220101030.852423-1-a-garg7@ti.com> (raw)
Configure Non-Transparent Bridge (NTB) components to build along with
J721E PCIe controller driver to add support for PCI NTB functionality
in TI SoCs.
NTB_NETDEV allows to setup a virtual ethernet interface over the
NTB Transport layer, enabling connected systems to communicate with
each other using standard network protocols and transfer data as
ethernet traffic over the link.
Signed-off-by: Aksh Garg <a-garg7@ti.com>
---
drivers/pci/controller/cadence/Kconfig | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/pci/controller/cadence/Kconfig b/drivers/pci/controller/cadence/Kconfig
index 9e651d545973..2da9d4ed3ed0 100644
--- a/drivers/pci/controller/cadence/Kconfig
+++ b/drivers/pci/controller/cadence/Kconfig
@@ -76,6 +76,10 @@ config PCI_J721E_HOST
depends on ARCH_K3 || COMPILE_TEST
depends on OF
select PCI_J721E
+ imply NTB
+ imply NTB_TRANSPORT
+ imply NTB_EPF
+ imply NTB_NETDEV
help
Say Y here if you want to support the TI J721E PCIe platform
controller in host mode. TI J721E PCIe controller uses Cadence PCIe
@@ -87,6 +91,7 @@ config PCI_J721E_EP
depends on OF
depends on PCI_ENDPOINT
select PCI_J721E
+ imply PCI_EPF_NTB
help
Say Y here if you want to support the TI J721E PCIe platform
controller in endpoint mode. TI J721E PCIe controller uses Cadence PCIe
--
2.34.1
next reply other threads:[~2026-02-20 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 10:10 Aksh Garg [this message]
2026-02-20 10:15 ` Siddharth Vadapalli
2026-03-05 4:55 ` Manivannan Sadhasivam
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=20260220101030.852423-1-a-garg7@ti.com \
--to=a-garg7@ti.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=danishanwar@ti.com \
--cc=hans.zhang@cixtech.com \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mpillai@cadence.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=unicorn_wang@outlook.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®