From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: <lpieralisi@kernel.org>, <kwilczynski@kernel.org>,
<mani@kernel.org>, <robh@kernel.org>, <bhelgaas@google.com>,
<jingoohan1@gmail.com>, <christian.bruel@foss.st.com>,
<krishna.chundru@oss.qualcomm.com>, <qiang.yu@oss.qualcomm.com>,
<shradha.t@samsung.com>, <thippeswamy.havalige@amd.com>,
<inochiama@gmail.com>, <fan.ni@samsung.com>, <cassel@kernel.org>,
<kishon@kernel.org>, <18255117159@163.com>,
<rongqianfeng@vivo.com>, <jirislaby@kernel.org>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>,
<s-vadapalli@ti.com>
Subject: [PATCH v5 0/4] PCI: Keystone: Enable loadable module support
Date: Wed, 29 Oct 2025 13:34:48 +0530 [thread overview]
Message-ID: <20251029080547.1253757-1-s-vadapalli@ti.com> (raw)
Hello,
This series enables support for the 'pci-keystone.c' driver to be built
as a loadable module. The motivation for the series is that PCIe is not
a necessity for booting Linux due to which the 'pci-keystone.c' driver
does not need to be built-in.
Series is based on 6.18-rc1 tag of Mainline Linux.
This series has __NO__ dependencies.
v4:
https://lore.kernel.org/r/20251022095724.997218-1-s-vadapalli@ti.com/
Changes since v4:
- To fix the build error on ARM32 platforms as reported at:
https://lore.kernel.org/r/202510281008.jw19XuyP-lkp@intel.com/
patch 4 in the series has been updated by introducing a new config
named "PCI_KEYSTONE_TRISTATE" which allows building the driver as
a loadable module. Additionally, this newly introduced config can
be enabled only for non-ARM32 platforms. As a result, ARM32 platforms
continue using the existing PCI_KEYSTONE config which is a bool, while
ARM64 platforms can use PCI_KEYSTONE_TRISTATE which is a tristate, and
can optionally enabled loadable module support being enabled by this
series.
Series has been compile tested with W=1 for ARM32 using
arm-none-linux-gnueabihf-gcc
Series has been tested for functionality on an ARM64 platform (AM65 SoC):
AM654-EVM with an NVMe SSD connected to the PCIe Connector of the EVM.
Test Logs:
https://gist.github.com/Siddharth-Vadapalli-at-TI/474a16037d990206e1d22399a93dfee7
Regards,
Siddharth.
Siddharth Vadapalli (4):
PCI: Export pci_get_host_bridge_device() for use by pci-keystone
PCI: dwc: Export dw_pcie_allocate_domains() and
dw_pcie_ep_raise_msix_irq()
PCI: keystone: Exit ks_pcie_probe() for invalid mode
PCI: keystone: Add support to build as a loadable module
drivers/pci/controller/dwc/Kconfig | 15 +++-
drivers/pci/controller/dwc/Makefile | 3 +
drivers/pci/controller/dwc/pci-keystone.c | 80 +++++++++++--------
.../pci/controller/dwc/pcie-designware-ep.c | 1 +
.../pci/controller/dwc/pcie-designware-host.c | 1 +
drivers/pci/host-bridge.c | 1 +
include/linux/pci.h | 1 +
7 files changed, 65 insertions(+), 37 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-29 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 8:04 Siddharth Vadapalli [this message]
2025-10-29 8:04 ` [PATCH v5 1/4] PCI: Export pci_get_host_bridge_device() for use by pci-keystone Siddharth Vadapalli
2025-10-29 8:04 ` [PATCH v5 2/4] PCI: dwc: Export dw_pcie_allocate_domains() and dw_pcie_ep_raise_msix_irq() Siddharth Vadapalli
2025-10-29 8:04 ` [PATCH v5 3/4] PCI: keystone: Exit ks_pcie_probe() for invalid mode Siddharth Vadapalli
2025-10-29 8:04 ` [PATCH v5 4/4] PCI: keystone: Add support to build as a loadable module Siddharth Vadapalli
2025-11-05 17:23 ` Manivannan Sadhasivam
2025-11-06 7:01 ` Siddharth Vadapalli
2025-11-06 8:00 ` Manivannan Sadhasivam
2025-11-13 18:13 ` Bjorn Helgaas
2025-11-13 18:35 ` Russell King (Oracle)
2025-11-13 18:48 ` Bjorn Helgaas
2025-11-06 8:10 ` [PATCH v5 0/4] PCI: Keystone: Enable loadable module support Manivannan Sadhasivam
2025-11-13 18:25 ` Bjorn Helgaas
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=20251029080547.1253757-1-s-vadapalli@ti.com \
--to=s-vadapalli@ti.com \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=christian.bruel@foss.st.com \
--cc=fan.ni@samsung.com \
--cc=inochiama@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=jirislaby@kernel.org \
--cc=kishon@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=qiang.yu@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=rongqianfeng@vivo.com \
--cc=shradha.t@samsung.com \
--cc=srk@ti.com \
--cc=thippeswamy.havalige@amd.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®