LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Haavard Skinnemoen" <hskinnemoen@atmel.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"Marc Pignat" <marc.pignat@hevs.ch>,
	wim@iguana.be, linux-kernel@vger.kernel.org
Subject: Re: [RFC, PATCH] watchdog on gpio
Date: Mon, 14 Jan 2008 07:22:39 -0500	[thread overview]
Message-ID: <8bd0f97a0801140422n3d3e3835v7f57dbe33c7a6db0@mail.gmail.com> (raw)
In-Reply-To: <20080114131429.40453e5f@siona>

On Jan 14, 2008 7:14 AM, Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:
> "Mike Frysinger" <vapier.adi@gmail.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

  reply	other threads:[~2008-01-14 12:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 15:11 Marc Pignat
2008-01-10 17:14 ` Ben Dooks
2008-01-11 16:40 ` Florian Fainelli
2008-01-14  7:34   ` Marc Pignat
2008-01-14  8:08   ` Mike Frysinger
2008-01-14  8:04 ` Mike Frysinger
2008-01-14  9:03   ` Alan Cox
2008-01-14  9:28     ` Mike Frysinger
2008-01-14  9:29       ` Alan Cox
2008-01-14  9:45         ` Mike Frysinger
2008-01-14 12:14           ` Haavard Skinnemoen
2008-01-14 12:22             ` Mike Frysinger [this message]
2008-01-14 13:30               ` Haavard Skinnemoen
2008-01-14 12:49           ` Johannes Weiner
2008-01-14 13:03             ` Mike Frysinger
2008-01-14 13:56               ` printk-wrapper with sectionized string constants [was: Re: [RFC, PATCH] watchdog on gpio] Johannes Weiner

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=8bd0f97a0801140422n3d3e3835v7f57dbe33c7a6db0@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.pignat@hevs.ch \
    --cc=wim@iguana.be \
    --subject='Re: [RFC, PATCH] watchdog on gpio' \
    /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

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).