From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: mochel@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [BKPATCH] bus notifiers for the generic device model
Date: Wed, 4 Dec 2002 10:13:53 -0800 [thread overview]
Message-ID: <20021204181353.GA28062@kroah.com> (raw)
In-Reply-To: <200212041804.gB4I4g803144@localhost.localdomain>
On Wed, Dec 04, 2002 at 12:04:41PM -0600, James Bottomley wrote:
> greg@kroah.com said:
> > But doesn't the bus specific core know when drivers are attached, as
> > it was told to register or unregister a specific driver? So I don't
> > see why this is really needed.
>
> The problem is that the bus specific core registration no-longer knows if the
> probes succeeded or failed (and if they did, what devices were attached),
> since probing is controlled by the base core.
Not quite. Well, I guess you can modify all of your drivers to do this,
but see below for an easier way.
> What the bus needs to know is when a driver attaches to a specific device (and
> what device it has attached to).
Why not have a call in the driver that notifies the bus specific core of
this? Or just check the status of the return value of your "probe"
function that the bus provides. See usb_device_probe() and
pci_device_probe() for examples of this.
thanks,
greg k-h
next prev parent reply other threads:[~2002-12-04 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 17:09 [BKPATCH] bus notifiers for the generic device model James Bottomley
2002-12-04 17:56 ` Greg KH
2002-12-04 18:04 ` James Bottomley
2002-12-04 18:04 ` Patrick Mochel
2002-12-04 18:42 ` Jeff Garzik
2002-12-05 3:33 ` Patrick Mochel
2002-12-04 18:13 ` Greg KH [this message]
2002-12-04 19:35 ` James Bottomley
2002-12-04 22:29 ` Greg KH
2002-12-05 3:50 ` Patrick Mochel
2002-12-05 16:14 ` James Bottomley
2002-12-05 16:57 ` Jeff Garzik
2002-12-06 19:10 ` Patrick Mochel
2002-12-04 18:10 ` Mike Anderson
2002-12-04 18:52 ` Greg KH
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=20021204181353.GA28062@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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