lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 14 Dec 2014 08:39:18 +0530
From:	sundeep subbaraya <>
To:	Paul Zimmerman <>
Cc:	"" <>,
	"" <>,
	"" <>
Subject: Re: query on DWC3

Hi Paul,

As per my understanding, for BULK OUT we do queue a request with 512
bytes length since we do not
know the length of the transfer Host is going to send. For Control OUT
we know the length in wLength of
Setup packet, hence I assumed there is no difference in programming
model of Control IN and OUT.
Now it is clear for me. Thanks for the clarification :)


On Sun, Dec 14, 2014 at 5:21 AM, Paul Zimmerman
<> wrote:
>> From: [] On Behalf Of sundeep subbaraya
>> Sent: Friday, December 12, 2014 9:13 PM
>> Hi Felipe,
>> In DWC3 driver, for three stage Control OUT transfer there is a check:
>>    else if (!IS_ALIGNED(req->request.length, dep->endpoint.maxpacket)
>>              && (dep->number == 0)) {.
>>     }
>> I understand that we check for alignment of sizes and if not we
>> prepare trb with maxpacket and enable interrupt on short packet. In
>> databook I could not find anything related to this, it talks only
>> about addresses should be aligned. In Control transfer programming
>> model there is no difference between Control OUT or IN transfer, if
>> three stage transfer - prepare trb with length wLength. Initially I
>> followed this and not able to receive data on EP0 OUT.:( .After adding
>> the above check it is working. Please help me to understand why we do
>> this?
> Hi Sundeep,
> Please see section "Buffer Size Rules and Zero-Length Packets"
> in the databook:
>         For OUT endpoints, the following rules apply:
>         - The total size of a Buffer Descriptor must be a multiple of
>           MaxPacketSize
> The wording may be a little confusing, it actually means that the size
> of the data buffer for OUT endpoints must be a multiple of MaxPacketSize.
> Section 8.2.5 states it more clearly:
>         - An OUT transfer’s transfer size (Total TRB buffer allocation)
>           must be a multiple of MaxPacketSize even if software is expecting
>         a fixed non-multiple of MaxPacketSize transfer from the Host.
> This rule applies to all OUT endpoint types, including Control endpoints.
> --
> Paul
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists