On Wed, 5 Dec 2007, Sarah Sharp wrote: > The macro MODULE_DEVICE_TABLE won't work when the id table is defined in > a different C file. If the table is defined in pl2303.c, then I think > the core would have to depend on the pl2303 driver, which seems > completely backwards. > > A friend suggested setting the reset-resume quirk for all devices and > then removing it later. However, this seems a little overboard. > > Any other suggestions?
Maybe the best thing is what we discussed earlier: Just have the pl2303 driver set the quirk when it sees that the device needs it. This seems preferable to maintaining two identical copies of the id table. Yes, this leaves open a window in which the quirk won't be set. If the driver isn't loaded then we don't really care whether or not the device survives being suspended. (Perhaps lsusb would run into trouble... it wouldn't be a big deal.) To make it work, you might need to add a call to usb_reset_composite_device() in the probe routine. You'll have to do some testing to see whether that is needed. Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
