[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9348609.HjKCmL9u9S@wuerfel>
Date: Thu, 07 Feb 2013 01:54:22 +0100
From: Arnd Bergmann <arnd@...db.de>
To: devicetree-discuss@...ts.ozlabs.org
Cc: Linus Walleij <linus.walleij@...aro.org>,
Thierry Reding <thierry.reding@...onic-design.de>,
Grant Likely <grant.likely@...retlab.ca>,
Greg KH <gregkh@...uxfoundation.org>,
Russell King <linux@....linux.org.uk>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Rob Herring <rob.herring@...xeda.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
linux-tegra@...r.kernel.org, Andrew Murray <andrew.murray@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 06/14] ARM: pci: Keep pci_common_init() around after init
On Wednesday 06 February 2013 17:38:20 Linus Walleij wrote:
> On Wed, Jan 9, 2013 at 9:43 PM, Thierry Reding
> <thierry.reding@...onic-design.de> wrote:
>
> > When using deferred driver probing, PCI host controller drivers may
> > actually require this function after the init stage.
> >
> > Signed-off-by: Thierry Reding <thierry.reding@...onic-design.de>
>
> There seem to be a proliferation of these patches now.
>
> Isn't this just papering over the real problem? The discarding
> of __init sections need to happen *after* all deferred probes
> are complete, lest we have to remove *all* __init sections from
> *all* drivers in the kernel, don't we?
No, I think it's not quite that bad. I think the rule is still
just that .probe() functions and anything called from them must
not be __init. They used to be __devinit, which would cause
problems with deferred probing on !HOTPLUG systems but that's
gone in 3.9.
Thierry's patch is just necessary because pci_common_init used
to be called only from actual __init functions, and not it
gets called from a .probe() function for the first time.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists