Am Donnerstag, 10. Oktober 2002 01:31 schrieb Johannes Erdfelt:
> On Thu, Oct 10, 2002, Oliver Neukum <[EMAIL PROTECTED]> wrote:
> > I've started looking at doing configurations correctly.
> > There are several questions.
> >
> > 1. Must it be legal for a driver to set configuration during probe ?
>
> This is tricky. There is a certain bit of coordination that is implied
> with selecting a configuration since it can change the interfaces
> available.
>
> We don't want to switch a configuration out from under another driver,
> nor do we want to switch a configuration before another interface is
> offered it.
>
> I'm not sure what the best answer here is and I'm sure how we choose the
> configuration will determine the answer to this question :)
I hope the answer is no. Else this'll be very painful.
> > 2. Is a patch that adds a struct usb_device* to struct usb_interface
> > acceptable?
>
> For what reason?
To allow sane locking. Locking for configuration changes must be on the level
of usb_device. Probing is done on usb_interface level.
> > 3. Where in the generic device model is the configuration stored
> > and how can it be manipulated ?
>
> Generic device? Like struct device?
Yes, it must be stored so it is available during resume().
> > 4. May I split usb_disconnect() into an interface and a usb_device
> > part ?
>
> Depends on the intent. If it's to notify a driver that the configuration
> changed out from underneath it and the interface no longer exists, sure.
>
> Other than that, you don't really "disconnect" an interface, but that's
> just wording.
Yes, I need infrastructure to "disconnect" the interface without disconnecting
the usb_interface.
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
