From: David Brownell <david-b@pacbell.net>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Cc: "Greg KH" <gregkh@suse.de>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>,
"Andres Salomon" <dilinger@debian.org>
Subject: Re: [patch 2.6.21-rc5-git 1/2] fix hotplug for legacy platform drivers
Date: Mon, 2 Apr 2007 13:17:22 -0700 [thread overview]
Message-ID: <200704021317.22909.david-b@pacbell.net> (raw)
In-Reply-To: <d120d5000704021310r777e1796rf2025d873404afeb@mail.gmail.com>
On Monday 02 April 2007 1:10 pm, Dmitry Torokhov wrote:
> On 3/31/07, David Brownell <david-b@pacbell.net> wrote:
> > @@ -349,6 +360,13 @@ EXPORT_SYMBOL_GPL(platform_device_unregi
> > * memory allocated for the device allows drivers using such devices
> > * to be unloaded iwithout waiting for the last reference to the device
> > * to be dropped.
> > + *
> > + * This interface is primarily intended for use with legacy drivers
> > + * which probe hardware directly. Because such drivers create device
> > + * nodes themselves, rather than letting system infrastructure handle
> > + * such device enumeration tasks, they don't fully conform to the Linux
> > + * driver model. In particular, when such drivers are built as modules,
> > + * they can't be "hotplugged".
> > */
> > struct platform_device *platform_device_register_simple(char *name, unsigned int id,
>
> I find this comment misleading. Many of these drivers do not create
> any devices (as in /dev/xxx) but rather create underlying hardware
> abstraction objects.
When I refresh this patch, I'll make it say "create sysfs device nodes" to
make clear which type of device node (not the /dev/ kind) it's referring to.
- Dave
prev parent reply other threads:[~2007-04-02 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 21:55 David Brownell
2007-04-02 10:49 ` Cornelia Huck
2007-04-02 16:59 ` David Brownell
2007-04-03 8:52 ` Cornelia Huck
2007-04-02 10:55 ` Russell King
2007-04-02 16:39 ` David Brownell
2007-04-02 20:10 ` Dmitry Torokhov
2007-04-02 20:17 ` David Brownell [this message]
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=200704021317.22909.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=dilinger@debian.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome