Thanks for the Response... The trouble is that unbinding the HUB from the kernel driver results if all the devices being removed from the system. In this case there are 2 USB audio codecs, a serial port chip and a custom controller out there that will drop off with it. When all i am trying to do is control one of them. My hope was that their would be an ioctl in KHubd that allows the user to turn off the ports without having to delete all of them. I sent port turn off commands in the hope that the HUB would trigger a Change interrrupt which khubd would get and do the right thing with. Thoughts ? -Lenny On Sun, Sep 18, 2011 at 10:19 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Sun, 18 Sep 2011, Lenny Story wrote: > >> Greetings, >> >> I am using a custom composite usb device with a known hub. It has per >> port power control, and when turned off i can confirm that the power >> is indeed off (via volt measurement). However, doing a followup >> "lsusb" the device still shows in the list. When i try to read the >> detailed descriptors, the device reports a timeout, although it still >> remains in lsusb list. >> >> Is there some API i am missing to get khubd to pickup the change ? > > No. The kernel's USB stack expects that only the hub driver will > communicate with hubs. If you go behind the hub driver's back to turn > off power to some ports, the results are unspecified. > >> I am using Libusb1.0 sending direct setFeature requests to the HUB. >> >> Thoughts anyone ? > > You should unbind the hub from the hub driver before messing with its > ports. Use libusb_detach_kernel_driver(). > > Alan Stern > > -- 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
