On 12.07.2017 08:30, Shyam Sundar S K wrote:
On 6/22/2017 4:34 PM, Mathias Nyman wrote:
On 22.06.2017 13:44, Shyam Sundar S K wrote:
On 6/19/2017 9:42 AM, Shyam Sundar S K wrote:
on AMD platforms with SNPS 3.1 USB controller if stop endpoint command is
issued the controller does not respond
On 6/22/2017 4:34 PM, Mathias Nyman wrote:
> On 22.06.2017 13:44, Shyam Sundar S K wrote:
>>
>> On 6/19/2017 9:42 AM, Shyam Sundar S K wrote:
>>> on AMD platforms with SNPS 3.1 USB controller if stop endpoint command is
>>> issued the controller does not respond, when the EP is not in running
>>>
On 6/22/2017 4:34 PM, Mathias Nyman wrote:
> On 22.06.2017 13:44, Shyam Sundar S K wrote:
>>
>> On 6/19/2017 9:42 AM, Shyam Sundar S K wrote:
>>> on AMD platforms with SNPS 3.1 USB controller if stop endpoint command is
>>> issued the controller does not respond, when the EP is not in running
>>>
On 22.06.2017 13:44, Shyam Sundar S K wrote:
On 6/19/2017 9:42 AM, Shyam Sundar S K wrote:
on AMD platforms with SNPS 3.1 USB controller if stop endpoint command is
issued the controller does not respond, when the EP is not in running
state. HW completes the command execution and reports
"Conte
On 6/19/2017 9:42 AM, Shyam Sundar S K wrote:
> on AMD platforms with SNPS 3.1 USB controller if stop endpoint command is
> issued the controller does not respond, when the EP is not in running
> state. HW completes the command execution and reports
> "Context State Error" completion code. This is
on AMD platforms with SNPS 3.1 USB controller if stop endpoint command is
issued the controller does not respond, when the EP is not in running
state. HW completes the command execution and reports
"Context State Error" completion code. This is as per the spec. However
HW on receiving the second co
