Re: hub port power control vs. physical disconnect/connect

["Vlado Handziski" <handzisk@xxxxxxxxxxxxxxxx>]

On Dec 12, 2007 4:20 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote:

> The USB stack doesn't remove a device until it gets a disconnect
> message from the device's hub.  When you turn off the port power the
> hub doesn't send any disconnect messages, so the kernel doesn't realize
> the device is gone.
>
> Currently there is no way for you to force this behavior (and there is
> no way to call usb_disconnect from userspace).  You can come close by
> unbinding the device's driver.  For example, if the device's sysfs ID
> was 1-2.3 you would do:
>
>        echo -n 1-2.3 >/sys/bus/usb/drivers/usb/unbind
>
> That won't remove the device structure but it will make the structure
> almost unusable.
>

Yes, we are already doing that (as shown in case 2 in the log at the
end of the original message). I was hoping that there is something
more that can be done that would either remove the device completely
or at least export somehow the info to sysfs that the structure below
this devce path is stale.

Vlado

-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
linux-usb-devel@xxxxxxxxxxxxxxxxxxxxx
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel