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>, <quic_wenbyao@quicinc.com>,
<inochiama@gmail.com>, <mayank.rana@oss.qualcomm.com>,
<thippeswamy.havalige@amd.com>, <shradha.t@samsung.com>,
<cassel@kernel.org>, <kishon@kernel.org>,
<sergio.paracuellos@gmail.com>, <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 v4 0/4] PCI: Keystone: Enable loadable module support
Date: Wed, 22 Oct 2025 15:27:08 +0530 [thread overview]
Message-ID: <20251022095724.997218-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.
DEPENDENCY
----------
This series has __NO__ dependencies since the dependencies stated in the
cover-letter of the v3 series at:
https://lore.kernel.org/r/20250922071222.2814937-1-s-vadapalli@ti.com/
have been satisfied.
v3:
https://lore.kernel.org/r/20250922071222.2814937-1-s-vadapalli@ti.com/
Changes since v3:
- Rebased series on 6.18-rc1 tag of Mainline Linux.
- Patch 4 has been updated to remove the '__init' keyword from functions
to avoid triggering an exception due to '__init' memory being freed
before functions are invoked. This is the equivalent of:
https://lore.kernel.org/r/20250912100802.3136121-3-s-vadapalli@ti.com/
while addressing Bjorn's feedback at:
https://lore.kernel.org/r/20251002143627.GA267439@bhelgaas/
by introducing a new 'init' function specifically for registering the
fault handler while the rest of the driver remains the same.
Series has been tested on AM654-EVM with an NVMe SSD connected to the
PCIe Connector of the EVM. Test Logs:
https://gist.github.com/Siddharth-Vadapalli-at-TI/332e8d65c66ed93e95c2d89ec1ee3f68
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 | 6 +--
drivers/pci/controller/dwc/pci-keystone.c | 38 +++++++++++++------
.../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 +
6 files changed, 33 insertions(+), 15 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-22 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 9:57 Siddharth Vadapalli [this message]
2025-10-22 9:57 ` [PATCH v4 1/4] PCI: Export pci_get_host_bridge_device() for use by pci-keystone Siddharth Vadapalli
2025-10-22 9:57 ` [PATCH v4 2/4] PCI: dwc: Export dw_pcie_allocate_domains() and dw_pcie_ep_raise_msix_irq() Siddharth Vadapalli
2025-10-22 9:57 ` [PATCH v4 3/4] PCI: keystone: Exit ks_pcie_probe() for invalid mode Siddharth Vadapalli
2025-10-22 9:57 ` [PATCH v4 4/4] PCI: keystone: Add support to build as a loadable module Siddharth Vadapalli
2025-10-28 3:06 ` kernel test robot
2025-10-28 4:54 ` Siddharth Vadapalli
2025-10-29 8:36 ` Siddharth Vadapalli
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=20251022095724.997218-1-s-vadapalli@ti.com \
--to=s-vadapalli@ti.com \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=inochiama@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=jirislaby@kernel.org \
--cc=kishon@kernel.org \
--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=mayank.rana@oss.qualcomm.com \
--cc=quic_wenbyao@quicinc.com \
--cc=robh@kernel.org \
--cc=rongqianfeng@vivo.com \
--cc=sergio.paracuellos@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).