On Wed, 20 Oct 2010, Sarah Sharp wrote: > > For testing purposes, it is best to imitate the behavior of a real > > device as closely as possible. USB-2.0 host controllers do not assign > > their own addresses to devices; they use the addresses provided by > > usbcore. I think this is also true for the low/full/high-speed > > components of a USB-3.0 controller. > > There is only one controller, the xHCI controller, that handles all > device speeds. There are no companion controllers for a USB 3.0 host > controller. The xHCI host controller uses the hardware assigned address > for all devices (LS/FS/HS/SS), not the usbcore address. I stand corrected. > But I'll admit I don't understand what dummy-hcd is supposed to do, so dummy-hcd is a virtual host controller/device controller combination. The virtual host controller has only one port, which is connected to the virtual device controller. The same computer acts as both host and gadget. The purpose is to allow testing of gadget drivers without the need for device-controller hardware. > I'm a bit confused as to why it needs an address_device function. Is it > supposed to be the gadget-side interface to the hardware that's > transmitting over USB (i.e. responding to the USB host)? Or does it > have something to do with a gadget switching over to host mode for OTG? In fact, dummy-hcd doesn't need or use the device address at all. And it doesn't support OTG. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
