From: James Bottomley <James.Bottomley@steeleye.com>
To: Greg KH <greg@kroah.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
mochel@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [BKPATCH] bus notifiers for the generic device model
Date: Wed, 04 Dec 2002 13:35:00 -0600 [thread overview]
Message-ID: <200212041935.gB4JZ0p03464@localhost.localdomain> (raw)
In-Reply-To: Message from Greg KH <greg@kroah.com> of "Wed, 04 Dec 2002 10:13:53 PST." <20021204181353.GA28062@kroah.com>
greg@kroah.com said:
> 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.
Well, I did do it this way for parisc. However, I assumed from reading the
driver model docs that we were transitioning to using the generic driver probe
rather than doing probe interceptions like this.
Doing it like this just seems rather clumsy. wouldn't it be better to
deprecate bus specific registrations in favour of the generic one?
There is another advantage to notifiers: they can be chained. Certain bus
architectures need to do additional setup for things like pci devices. They
would be able to do this by attaching a notifier.
James
next prev parent reply other threads:[~2002-12-04 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 17:09 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
2002-12-04 19:35 ` James Bottomley [this message]
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=200212041935.gB4JZ0p03464@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=greg@kroah.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
Powered by JetHome