On Thu, 26 Feb 2015, Mathias Nyman wrote:
> On 26.02.2015 16:57, Alan Stern wrote:
> > On Thu, 26 Feb 2015, Mathias Nyman wrote:
> >
> >> I'm starting to like your idea of setting the urb->actual_length in
> >> advance,
> >> It may actually simplify things.
> >
> > But it will make unlinking mo
On 26.02.2015 16:57, Alan Stern wrote:
> On Thu, 26 Feb 2015, Mathias Nyman wrote:
>
>> I'm starting to like your idea of setting the urb->actual_length in advance,
>> It may actually simplify things.
>
> But it will make unlinking more difficult. Also, what will you do if
> there is more than
On Thu, 26 Feb 2015, Mathias Nyman wrote:
> I'm starting to like your idea of setting the urb->actual_length in advance,
> It may actually simplify things.
But it will make unlinking more difficult. Also, what will you do if
there is more than one TRB?
Alan Stern
--
To unsubscribe from this l
...
>
> The second event is always COMP_SUCCESS and the event->transfer_len is
> always set to 0 in that one. The 3 cases I've seen are:
>
> case 1: 1 event on last TRB
> COMP_SUCCESS, event->len=0
>
> case 2: short event but with data
> COMP_SHORT_TX, event->len < urb->transfer_buffer_len
When a control transfer has a short data stage, the xHCI controller
generates
two transfer events: a COMP_SHORT_TX event that specifies the untransferred
amount, and a COMP_SUCCESS event. But when the data stage is not short,
only the
COMP_SUCCESS event occurs. There
On 23.02.2015 19:02, Aleksander Morgado wrote:
> On Mon, Feb 23, 2015 at 4:23 PM, Mathias Nyman
> wrote:
>> Hi
>>
>> On 23.02.2015 13:52, Aleksander Morgado wrote:
>>> When a control transfer has a short data stage, the xHCI controller
>>> generates
>>> two transfer events: a COMP_SHORT_TX event
On Mon, Feb 23, 2015 at 4:23 PM, Mathias Nyman
wrote:
> Hi
>
> On 23.02.2015 13:52, Aleksander Morgado wrote:
>> When a control transfer has a short data stage, the xHCI controller generates
>> two transfer events: a COMP_SHORT_TX event that specifies the untransferred
>> amount, and a COMP_SUCCES
Hi
On 23.02.2015 13:52, Aleksander Morgado wrote:
> When a control transfer has a short data stage, the xHCI controller generates
> two transfer events: a COMP_SHORT_TX event that specifies the untransferred
> amount, and a COMP_SUCCESS event. But when the data stage is not short, only
> the
> CO
When a control transfer has a short data stage, the xHCI controller generates
two transfer events: a COMP_SHORT_TX event that specifies the untransferred
amount, and a COMP_SUCCESS event. But when the data stage is not short, only the
COMP_SUCCESS event occurs. Therefore, xhci-hcd must set urb->act
