RE: Gadget driver rules question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 
> Is it normal that a gadget driver after creating a few IN endpoints does
> not start feeding any Tx data to some of them?
Yes, it is possible. It is gadget itself behave, it can call ->ep_enable to
create class endpoints after receiving SetInterface(1,1), then ->ep_enqueue
is triggered by application.

> 
> I'm asking because I thought it is strange but specifically g_serial  as
> of 2.6.34 (can't test this on any newer yet) by default and while no-one
> opens any ports yet (just cable plugged in), does this:
> 
> 1. creates IN1 bulk, IN2 intr. (I'm omitting OUTs here)
> 2. enqueues something to IN2, but _never_ enqueues anything to IN1 as
> far as I can see.
> 
> As soon as a token for IN1 arrives from the host, device driver gets
> stuck waiting indefinitely because it has nothing to send. What should
> it do in such case?
" waiting indefinitely" what do you mean? If there is no data to send, the
controller will send NAK automatically.

> 
> 
> Thank you.
> Nikolai
> --
> 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


--
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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux