The usb_set_interface() call sets this ... if drivers always (and only) use that in their probe() routines, and don't issue SET_INTERFACE calls directly (bypassing that), there's no problem keeping that in sync with the device state.
On the other hand, the probe() sequence modifies that field without invoking usb_set_interface(), so until the drivers' probe() routine issues that call, device and usbcore state will indeed be out of sync. - Dave ----- Original Message ----- From: "Gordon McNutt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 30, 2002 3:46 PM Subject: [linux-usb-devel] act_altsetting > I noticed that struct usb_interface_descriptor has this field. I'm > curious -- how does this field stay in synch with the device state? Does > the usb core peep on SETUP packets sent to the device's default control > pipe? > > Regards, > --gmcnutt > > > _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
