Yeah, that part's been a mess for a long time. The initial Linux-USB OTG implementation (OMAP1) had stub routines with printfs, which could be substituted for LED blinking or whatever. It sufficed at the time, what can I say! I forget which of the several drivers hosted those routines ... but you're right to imply that such support should be driver-neutral, and generic enough to swap message handling (or possibly, in userspace, messages; let them be translated, improved, etc.) without replacing the low-level routines called to report the errors. ISTR those routines vanished at some point without regard for OTG spec conformance (someone just didn't like printks). there was a fairly comprehensive set of call sites for the various errors called out by the then-current OTG spec, and diagnostics were as unique as practical at the time. A better solution would be a Good Thing; we are getting a surprising amount of OTG support lately, and all drivers should end up with the same solution to this problem. - Dave -- 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
