On Wed, 9 May 2007 10:09:33 -0700 (PDT), [EMAIL PROTECTED] wrote: > > Hm, so that sound like a case for a distinct setup() routine: > > > > 1. bus calls ->probe(), which return synchronously > > 2. bus calls ->probe_async() for all devices (optional) > > 3. bus waits for all probes to finish > > 4. bus calls ->setup() for all devices (which does the registering) > > this is exactly what I've been trying to describe.
Nearly, but with a slightly different spin... > > > (->setup() can but need not be sync, although it should be for your > > case) > > if it's not sync then you have race conditions again ...but not all busses will care. If your bus wants to enforce ordering, it must enforce it to be sync. If your bus allows hotplug and calling setup() later on, it may also allow async. (setup() is a bit dual-purpose in this idea.) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
