Hi Alan, In an upcoming patchset, I'm going to need to walk the USB tree in the xHCI driver in order to gather some information during a device configuration or alt setting change. Is there anything stopping the USB tree from changing while this operation is in progress? I think I remember some USB device locks and some bus mutexes in the USB core, but I think it would really be a layering violation if the xHCI driver grabbed those. A bit of background: I'm going to need to walk the tree, starting from the device under the roothub, and capturing information about pretty much all of its children. I may be able to cache some information about the devices as their endpoints are added by the xHCI driver later as an optimization. However, when I started down that path, I basically ended up with a tree-like structure similar to what the USB core has. So I'd rather re-use the USB core's tree in usb_device->children[] if I can. Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
