From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Fri, 12 Jan 2001 16:42:23 +0000 Subject: Re: hotplug TTD Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Andrew, > > 1: yenta driver sees the card insertion. schedules a call to > > pci_insert_device > > We should actually change this, and do it only for the case where we don't > already have a driver for the device. Why? It's a "here's a new device" notification, being called when there's a new device! It might be reasonable to have a _separate_ notification for the "this device has no driver" case, but those "new device" notifications will still be needed. > If we have a driver fior the device, > we should assume that it is the drivers responsibility to notify the > system about higher-level events. Not all higher level events; just some of them. Potentially. The hotplug events in the current system are primarily what one could call "container" notifications: bus subsystems (USB, PCI) reporting add/remove events for their devices, or the network subsystem reporting register/unregister events at the higher level that it works with (above busses, below apps). I don't think we want to encourage every driver to call some user mode helper directly, though I'm willing to accept that as a useful tool for rare cases. (Your async/sync fixes are helpful there, even enabling such calls in_interrupt.) The overall system has to be manageable and simple; encouraging lots of per-driver variation doesn't lead that direction. - Dave _______________________________________________ Linux-hotplug-devel mailing list Linux-hotplug-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel