On Wed, Sep 3, 2014 at 8:19 PM, Felipe Balbi <balbi@xxxxxx> wrote: > On Wed, Sep 03, 2014 at 02:48:43PM +0530, Anjana V Kumar wrote: >> Hi, >> >> This is regarding an issue we are facing with the gadget serial driver >> (driver/usb/gadget/serial.c). >> >> We have a hardware limitation and the USB hardware can only have >> bconfigurationvalue 0 or 1. > > what kind of limitation is this. Configuration value is a SW-only > choice. What HW are you using ? Which kernel are you using ? Do you have > logs of the problem ? > I am using 3.10 kernel. The issue is that the set_configuration(2) is stalled, while the set_configuration(1) passes with the USB hardware I am using. >> In the CDC ACM config in gadget serial driver the configuration value >> is set to 2. Is there a specific reason why this was done? >> >> We see that, the three configurations listed in serial driver (CDC >> ACM, CDC OBEX, generic serial) cannot be present together as per the >> current implementation. Is there a specific reason why the >> configuration values were set as 1, 2 and 3 instead of setting all to >> 1? > > well, setting configuration 0 means that you're not selecting any > configuration. Basically you go back to "Addressed" state, so you can't > use configuration 0 for anything, really. > Sorry for not being clear, I am not setting the configuration to 0. The question was, can we set all the three configuration values of CDC ACM, CDC OBEX, and generic serial to 1? Was there any specific reason as to why the configuration values were set as 1,2 and 3. We cannot have all three at the same time according to the current "if, elseif, else" implementation, > -- > balbi -- Anjana -- 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
