[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a0801140422n3d3e3835v7f57dbe33c7a6db0@mail.gmail.com>
Date: Mon, 14 Jan 2008 07:22:39 -0500
From: "Mike Frysinger" <vapier.adi@...il.com>
To: "Haavard Skinnemoen" <hskinnemoen@...el.com>
Cc: "Alan Cox" <alan@...rguk.ukuu.org.uk>,
"Marc Pignat" <marc.pignat@...s.ch>, wim@...ana.be,
linux-kernel@...r.kernel.org
Subject: Re: [RFC, PATCH] watchdog on gpio
On Jan 14, 2008 7:14 AM, Haavard Skinnemoen <hskinnemoen@...el.com> wrote:
> "Mike Frysinger" <vapier.adi@...il.com> wrote:
> > there is no hard requirement anywhere that says platform resources
> > must be in the board resources file. marking the functions as __init
> > instead of __devinit will basically cause a kernel crash if someone
> > tries to use dynamic platform resources. there is no option that i'm
> > aware of that prevents dynamic platform resources which means there is
> > no way for the driver to say "i wont work with standard dynamic
> > platform resources".
>
> There is: platform_driver_probe(). It takes the probe function as a
> parameter so that it can be left out of the platform_driver struct.
> After it returns, there are no references to the probe function left
> around, so if you call platform_driver_probe() instead of
> platform_driver_register(), the probe function can be __init.
ah, thanks for that. i think in that case, there's no way to bind the
release function to the process ? which means the driver is no longer
unloadable ? which means the platform driver release function can be
scrubbed as well as the module exit function as well as changing the
Kconfig to be a bool ?
-mike
--
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