On Tue, 17 Jun 2014, Vlad Ungureanu wrote: > To go into ADK mode the host needs to send the Android device a series of usb > control messages with different data. This yes can be done from userspace but > when the device goes into the ADK mode I need to handle it into Kernel space. > The end goal of the project is to simulate the displayLink driver using an > Android device instead of a DisplayLink compatible screen. In ADK mode I will > need just interface 1 which has 2 bulk EPs. No other interaction from userspace > will be with the device in ADK mode. Have you considered what will happen if your driver is present but the user wants the device to remain in its usual mode, rather than in ADK mode? Such problems are part of the reason why programs like usb-modeswitch exist. 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
