From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>, <lpieralisi@kernel.org>,
<kwilczynski@kernel.org>, <robh@kernel.org>,
<bhelgaas@google.com>, <jingoohan1@gmail.com>,
<fan.ni@samsung.com>, <quic_wenbyao@quicinc.com>,
<namcao@linutronix.de>, <mayank.rana@oss.qualcomm.com>,
<thippeswamy.havalige@amd.com>, <quic_schintav@quicinc.com>,
<shradha.t@samsung.com>, <inochiama@gmail.com>,
<cassel@kernel.org>, <kishon@kernel.org>, <18255117159@163.com>,
<rongqianfeng@vivo.com>, <jirislaby@kernel.org>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>
Subject: Re: [PATCH 00/11] PCI: Keystone: Enable loadable module support
Date: Mon, 8 Sep 2025 12:43:23 +0530 [thread overview]
Message-ID: <5825153e-833b-4aed-bbd5-e0f58e922aa0@ti.com> (raw)
In-Reply-To: <2gzqupa7i7qhiscwm4uin2jmdb6qowp55mzk7w4o3f73ob64e7@taf5vjd7lhc5>
On Mon, Sep 08, 2025 at 09:09:08AM +0530, Manivannan Sadhasivam wrote:
> On Wed, Sep 03, 2025 at 06:14:41PM GMT, Siddharth Vadapalli wrote:
> > 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.
> >
>
> There are concerns from the irqchip maintainers that unloading an irqchip
> controller is a bad idea. We had a lot of previous discussions on this topic.
Ok, I wasn't aware of this. Thank you for pointing this out.
>
> But I would certainly welcome the idea of building a controller driver as a
> module (tristate) and prevent unloading it during runtime (by keeping it as
> builtin_platform_driver).
I will update the series to retain 'builtin_platform_driver' while
enabling tristate support. Since the intent of the series is primarily
to convert the driver to support being built as a loadable module, and
unloading it is only a secondary requirement which is optional, I agree
with your suggestion.
>
> > Series is based on linux-next tagged next-20250903.
> >
>
> No need to base your patches on top of linux-next. Either do it on top of -rc1
> or pci/next.
I will keep this in mind when I post the v2 series.
Thank you for your feedback.
Regards,
Siddharth.
prev parent reply other threads:[~2025-09-08 7:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 12:44 [PATCH 00/11] PCI: Keystone: Enable loadable module support Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 01/11] PCI: Export pci_get_host_bridge_device() for use by pci-keystone Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 02/11] PCI: dwc: Export dw_pcie_allocate_domains() for pci-keystone Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 03/11] PCI: dwc: Add dw_pcie_free_domains() helper for cleanup Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 04/11] PCI: dwc: ep: Export dw_pcie_ep_raise_msix_irq() for pci-keystone Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 05/11] PCI: keystone: Add ks_pcie_free_msi_irq() helper for cleanup Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 06/11] PCI: keystone: Add ks_pcie_free_intx_irq() " Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 07/11] PCI: keystone: Add ks_pcie_host_deinit() " Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 08/11] PCI: keystone: Add ks_pcie_disable_error_irq() " Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 09/11] PCI: keystone: Switch to devm_request_irq() for "ks-pcie-error-irq" IRQ Siddharth Vadapalli
2025-09-04 7:24 ` Jiri Slaby
2025-09-04 9:12 ` Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 10/11] PCI: keystone: Exit ks_pcie_probe() for the default switch-case of "mode" Siddharth Vadapalli
2025-09-03 12:44 ` [PATCH 11/11] PCI: keystone: Add support to build as a loadable module Siddharth Vadapalli
2025-09-06 21:37 ` kernel test robot
2025-09-08 3:39 ` [PATCH 00/11] PCI: Keystone: Enable loadable module support Manivannan Sadhasivam
2025-09-08 7:13 ` Siddharth Vadapalli [this message]
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=5825153e-833b-4aed-bbd5-e0f58e922aa0@ti.com \
--to=s-vadapalli@ti.com \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=fan.ni@samsung.com \
--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=namcao@linutronix.de \
--cc=quic_schintav@quicinc.com \
--cc=quic_wenbyao@quicinc.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