Anjana V Kumar wrote:
> 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.
What USB hardware are you using?
Why not look into the actual problem with SET_CONFIGURATION? You may
discover things
Hi All,
Can you please help me understand the assignment of
bConfigurationValue in gadget serial driver.
As I had mentioned in my previous mail,
I agree that no two configurations can have same bConfigurationValue,
but in this case, the implementation is (drivers/usb/gadget/serial.c)
247
On Thu, Sep 4, 2014 at 7:38 PM, Alan Stern wrote:
> On Thu, 4 Sep 2014, Anjana V Kumar wrote:
>
>> >> 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 reas
On Thu, 4 Sep 2014, Anjana V Kumar wrote:
> >> 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
On Wed, Sep 3, 2014 at 8:19 PM, Felipe Balbi 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 on
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 limitat