> > > No. It requests the device to get de-configured, i.e. enter the
> > > ADDRESSED state. ... See USB spec 9.4.7.
> >
> > So are you suggesting that we not provide a way to re-enter that state?
>
> No, I do agree with you saying this is missing and it's worth having it.
I'll add it.
This'll need some work for hubs though. It's not as simple as it seems.
> Yes, that would be useful. For example, it provides some kind of partial
> reset. Forcing a device to go through the ADDRESS state should cause it to
> re-initilize pretty much of its features. Compared to driving a RESET
> condition on the bus the advantage is the address doesn't change.
Potentially very useful.
> I think we need some entity which takes responsibility to manage the
> device as a whole. We should offer drivers a way to say "I'll do this".
> If there is no such driver willing to manage the device, usbcore will try
> it's best for the per-interface drivers like it is doing now.
>
> I'm not saying we need to change the device probe model. Maybe it's
> sufficient to introduce the rule that drivers that have any of
> USB_DEVICE_ID_MATCH_VENDOR / _PRODUCT or _DEV_* in the match_flags for the
> probed device get the whole device granted - those with _INT_* only the
> interface. That would just be a extension of the match_flag semantics.
> OTOH this might get into conflict with some device-fixup code from
> usbserial and/or storage...
Nope, this is very unclean. If there turns out to be a real need to do
this, we'll switch to a two stage discovery.
Regards
Oliver
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
