> the device to be locked while resuming a child -- thereby preventing the
> possibility that the resume task could interfere with another task trying
> to suspend the device. �And individual drivers might want to use the lock
> for other purposes too (such as device resets).
>
>
> Not by coincidence, the scheme I've arrived at is essentially the one used
> in usbcore. �Basically, I'm suggesting that it be formalized and made to
> apply to the entire device-tree and power-hierarchy.
That seems reasonable, but how specific to USB is it? I suggest that
you use bluetooth as the worst case for this problem.
Wouldn't a rwsem per bus not be an adequate, generic solution?
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
