From: Kishon Vijay Abraham I <kishon@ti.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
<linux-kernel@vger.kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Bjorn Helgaas <bhelgaas@google.com>, <devicetree@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Grant Likely <grant.likely@linaro.org>,
Ley Foon Tan <lftan@altera.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Stanimir Varbanov <svarbanov@mm-sol.com>,
Thierry Reding <thierry.reding@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>, <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 0/5] Modularize PCI_DW related drivers.
Date: Wed, 24 Feb 2016 11:39:26 +0530 [thread overview]
Message-ID: <56CD4916.3050904@ti.com> (raw)
In-Reply-To: <1454889644-27830-1-git-send-email-paul.gortmaker@windriver.com>
Hi,
On Monday 08 February 2016 05:30 AM, Paul Gortmaker wrote:
> In a recent patch series that aimed to remove code related to module
> unload for PCI support that was simply non modular, the discussion
> led to people wanting to keep the code and push towards taking the
> steps needed to support moving it towards tristate instead[1].
>
> Here, we take step one, which is simply making the Kconfig change
> and then dealing with any build fallout or modpost fallout. What
> amounts to essentially a sanity build test. To be clear, these
> have not been runtime validated; that will need to be done by those
> with access to real hardware. However, the changes are not anything
> that should disrupt any existing built-in validation, so real world
> users should not be impacted by this change.
>
> We start with a smaller family of drivers; those that actively select
> PCI_DW, as a nice self contained group to test the waters and see if
> everyone is still good with this approach before investing more time
> on a wider scale to other pci/host/ code blocks.
>
> As such the drivers here share a dependency on having the same group
> of functions exported in order to successfully complete modpost.
>
> In addition, we have to stray outside drivers/pci to add exports
> in two places; once for an ARM fault handler, and once for an OF
> variable.
>
> The pci-keystone-dw.c instance was handled separately because it
> consists of two source files that need their own group of driver
> specific exports above and beyond the "shared" ones.
>
> Then we convert the Kconfig for all remaining at once; we could have
> done it on a per driver basis for ease of revert if anyone really
> objects, but since it would be a one line change, that seemed like
> not a real concern.
>
> Build testing was done on the linux-next tree for arm allmodconfig.
I took these patches and gave a test with DRA7xx board. As expected there was
no issues when the driver was built-in. However when I tried to rmmod/modprobe
I got this error [2].
Thanks
Kishon
[2] -> http://pastebin.ubuntu.com/15185894/
>
> [1] https://lkml.kernel.org/r/20160108203102.GH5354@localhost
>
next prev parent reply other threads:[~2016-02-24 6:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 0:00 [PATCH 0/5] Modularize PCI_DW related drivers Paul Gortmaker
2016-02-08 0:00 ` [PATCH 3/5] drivers/pci: export dw syms enabling board specific PCI code to be tristate Paul Gortmaker
2016-02-08 9:57 ` Arnd Bergmann
2016-02-08 15:53 ` Paul Gortmaker
2016-02-08 0:00 ` [PATCH 4/5] drivers/pci: make host/pci-keystone-dw.c modular Paul Gortmaker
2016-02-08 9:59 ` Arnd Bergmann
2016-02-08 15:53 ` Paul Gortmaker
2016-02-08 19:03 ` Murali Karicheri
2016-02-08 0:00 ` [PATCH 5/5] drivers/pci: make most of the PCI_DW drivers modular Paul Gortmaker
2016-02-08 10:00 ` Arnd Bergmann
2016-02-08 15:51 ` Paul Gortmaker
2016-02-24 6:09 ` Kishon Vijay Abraham I [this message]
2016-02-24 9:04 ` [PATCH 0/5] Modularize PCI_DW related drivers Arnd Bergmann
2016-02-25 8:13 ` Kishon Vijay Abraham I
2016-02-25 8:35 ` Arnd Bergmann
2016-02-29 9:29 ` Kishon Vijay Abraham I
2016-03-01 21:35 ` Arnd Bergmann
2016-03-15 20:50 ` Murali Karicheri
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=56CD4916.3050904@ti.com \
--to=kishon@ti.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=grant.likely@linaro.org \
--cc=lftan@altera.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m-karicheri2@ti.com \
--cc=paul.gortmaker@windriver.com \
--cc=robh+dt@kernel.org \
--cc=svarbanov@mm-sol.com \
--cc=thierry.reding@gmail.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 NNTP newsgroup(s).