>> # usb_notifier_list is blocking_notifier and may not be time effective, not only OTG 1.3 >but also OTG 2.0, there are a lot of timing requirement per spec. >> For some case, we need the event notification happened asap. So I add an unified >interface here and then let each otg implementation to bind its actual handler for these >events. > >Sorry, but no, I really doubt your notification time limits are somehow >not met with the existing notifiers. Please show me where they are out >of range for your usage. > Hi Greg, As mentioned by Pavan in another email, OTG state should be moved from A_WAIT_BCON to A_HOST when "B-device connection" event detected. The timeout can be as small as 1.1 sec. Another case is happened during OTG HNP. When it is in A_SUSPEND, it will move to A_PERIPHERAL state upon a "B-device disconnect" event. The timeout can be as small as 200 msec. So using existing blocking notifier may not be good enough. Thanks Hao -- 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
