On Thu, Jan 22, 2004 at 01:15:06AM -0800, John Heil wrote: > > I've noticed that at probe time, struct usb_interface->class_dev == 0 > even though struct usb_bus defines struct class_device class_dev. > The usb_bus address is not conveyed to the struct interface. > > Is this an omission in interface setup: core/config.c ? > > Seems so...
No. > I want to use struct class_device->class_data for a common/shared, > multi-driver control block common to multiple custom devices > on the same bus. Sorry, you can't do that. But my other question would be, why in the world would you want to do that using the usb structures, and not just have your usb devices register themselves with your "control block" logic, like all other USB devices do (like input, tty, network, etc...)? > There does not seem to be a simple way to do this w/in the > scope of available usb structure private fields. > > Any suggestions or should I do a patch for core/config.c??? A usb_bus is a struct class_device, right? That data is used to create the /sys/class/usb_host/ files. That is not available for any USB drivers to use, only the usb host controller drivers. thanks, greg k-h ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
