From: Johan Hovold <johan@kernel.org>
To: Stanimir Varbanov <svarbanov@mm-sol.com>
Cc: "Johan Hovold" <johan+linaro@kernel.org>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: qcom: Add support for modular builds
Date: Thu, 14 Jul 2022 15:10:29 +0200 [thread overview]
Message-ID: <YtAVxZJZmsxjytNp@hovoldconsulting.com> (raw)
In-Reply-To: <cc7c90aa-6705-7493-2f58-5112f7d663a3@mm-sol.com>
On Thu, Jul 14, 2022 at 03:19:49PM +0300, Stanimir Varbanov wrote:
> Hi Johan,
>
> Please take a look why we made it built-in first [1].
>
> If arguments there are still valid I don't see why to make it a module
> again.
Yeah, I've seen that patch, and many just like that one by the same
author, and I don't think the arguments spelled out there are valid.
Sure, the Kconfig symbol for this driver was bool at the time so the
remove() code could not have received much testing, but the patch
ignores the fact that preventing drivers to be built as modules is
detrimental to multi-platform builds (e.g. Android GKI).
As I mention in passing below, being able to build a driver as a module
is also really useful during development. Not least to be able to test
power-sequencing and making sure that you're not unknowingly relying on
boot firmware to have set things up for you.
> [1] https://lkml.org/lkml/2016/8/24/694
>
> On 5/19/22 12:46, Johan Hovold wrote:
> > Allow the Qualcomm PCIe controller driver to be built as a module, which
> > is useful for multi-platform kernels as well as during development.
> >
> > Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
> > ---
> > drivers/pci/controller/dwc/Kconfig | 2 +-
> > drivers/pci/controller/dwc/pcie-qcom.c | 36 +++++++++++++++++++++++---
> > 2 files changed, 34 insertions(+), 4 deletions(-)
Johan
next prev parent reply other threads:[~2022-07-14 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 9:46 Johan Hovold
2022-05-26 20:53 ` Rob Herring
2022-06-23 11:40 ` Johan Hovold
2022-06-23 15:52 ` Bjorn Helgaas
2022-06-27 7:31 ` Johan Hovold
2022-07-14 12:19 ` Stanimir Varbanov
2022-07-14 13:05 ` Dmitry Baryshkov
2022-07-15 16:56 ` Bjorn Helgaas
2022-07-18 7:43 ` Stanimir Varbanov
2022-07-14 13:10 ` Johan Hovold [this message]
2022-07-20 16:27 ` Manivannan Sadhasivam
2022-07-20 21:20 ` Bjorn Helgaas
2022-07-21 6:51 ` Johan Hovold
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=YtAVxZJZmsxjytNp@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=svarbanov@mm-sol.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®