Vlad Ungureanu <vvu@xxxxxxx> writes: >> On Tue, 2014-06-17 at 11:18 +0200, Vlad Ungureanu wrote: >> > > >> >> > > If that is not your intention, then you need to be more specific in the match table. >> > Yes, it matches the whole device so that is why every interface gets probed. I >> > will change that. >> >> That's problematic. You need to find out what happens if both interfaces >> are used at the same time. > > My device has 2 interfaces in normal mode and 2 interfaces in ADK mode. > Interface 0 has just ep0 which is control endpoint. Interface 1 has 2 bulk EPs: > IN, OUT. I should check the macro how to define them nicely in the device > table. That sounds like a normal CDC control + data interface arrangement, where 2 interfaces are used for 1 function. Typically grouped by a CDC Union functional descriptor and/or an Interface Association Descriptor. You should check out some of the existing communication class drivers, like the cdc-acm driver Oliver pointed to. There is also cdc_ether, cdc_ncm, cdc_mbim and probably others. Bjørn -- 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
