[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <410670D7E743164D87FA6160E7907A56FD9F6775@am04wembxb.internal.synopsys.com>
Date: Mon, 3 Apr 2017 05:32:23 +0000
From: Minas Harutyunyan <Minas.Harutyunyan@...opsys.com>
To: Felipe Balbi <balbi@...nel.org>,
Minas Harutyunyan <Minas.Harutyunyan@...opsys.com>,
John Youn <John.Youn@...opsys.com>,
"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dwc2: gadget: Fix in control write transfers
Hi,
On 3/30/2017 2:42 PM, Felipe Balbi wrote:
>
> Hi,
>
> Minas Harutyunyan <Minas.Harutyunyan@...opsys.com> writes:
>> After data out stage gadget driver should not initate ZLP on control EP,
>> because it is up to function driver.
>
> not true always, depends on return value from ->setup(). Which problem
> did you have? Which gadget driver? How did you reproduce? Which other
> tests did you run on this patch?
>
This required for delayed status support. Tested with Synopsys test
gadget. As host used USB tracer traffic generator (different control
transfers scenarios). Also performed smoke tests with mass storage
function to detect any side effects.
Thanks,
Minas
Powered by blists - more mailing lists