Hello All, OTG specification mandates "No silent failures. But the specification does not tell the exact error message and recommends the message to be self explanatory. The following are some of the error scenario examples. 1. Peripheral is not connected with in Ta_WAIT_BCON time. 2. Peripheral is not responding for HNP enable requests. 3. The attached peripheral is not supported. (Not found in TPL). 4. HUB class is not supported. (It falls into (3). But spec asks to distinguish the error message between hub and non-hub devices) 5. HNP failed 6. A-device did not respond for SRP (2), (3) and (4) conditions are identified by the HUB driver and remaining can be taken care by HCD/OTG driver. In Linux kernel we don't have a mechanism/framework for USB core/OTG driver to notify the above errors to user space. Can we have a utility like otg_notify_error(enum usb_otg_error) in drivers/usb/otg.c to send an uevent to userspace upon an error condition? We should also have a common header file between kernel and users pace for error code mapping. If the above proposal is okay, I will send patches for review comments. Thanks in advance, Pavan -- Sent by a consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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
