[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2gzqupa7i7qhiscwm4uin2jmdb6qowp55mzk7w4o3f73ob64e7@taf5vjd7lhc5>
Date: Mon, 8 Sep 2025 09:09:08 +0530
From: Manivannan Sadhasivam <mani@...nel.org>
To: Siddharth Vadapalli <s-vadapalli@...com>
Cc: lpieralisi@...nel.org, kwilczynski@...nel.org, robh@...nel.org,
bhelgaas@...gle.com, jingoohan1@...il.com, fan.ni@...sung.com,
quic_wenbyao@...cinc.com, namcao@...utronix.de, mayank.rana@....qualcomm.com,
thippeswamy.havalige@....com, quic_schintav@...cinc.com, shradha.t@...sung.com,
inochiama@...il.com, cassel@...nel.org, kishon@...nel.org, 18255117159@....com,
rongqianfeng@...o.com, jirislaby@...nel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, srk@...com
Subject: Re: [PATCH 00/11] PCI: Keystone: Enable loadable module support
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.
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).
> 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.
- Mani
--
மணிவண்ணன் சதாசிவம்
Powered by blists - more mailing lists