Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To:     Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>,
        "balbi@kernel.org" <balbi@kernel.org>,
        "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
CC:     "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "Thinh.Nguyen@synopsys.com" <Thinh.Nguyen@synopsys.com>,
        "v.anuragkumar@gmail.com" <v.anuragkumar@gmail.com>
Subject: Re: [PATCH v4 6/8] usb: dwc3: check for requests in started list
 for stream capable endpoints
Thread-Topic: [PATCH v4 6/8] usb: dwc3: check for requests in started list
 for stream capable endpoints
Thread-Index: AQHUR4UYRgxFEofqUUKoe+A6FKwC1w==
Date:   Mon, 10 Sep 2018 22:50:44 +0000
Message-ID: <30102591E157244384E984126FC3CB4F544ADF4D@us01wembx1.internal.synopsys.com>
References: <1536418986-16609-1-git-send-email-anurag.kumar.vulisha@xilinx.com>
 <1536418986-16609-7-git-send-email-anurag.kumar.vulisha@xilinx.com>
 <30102591E157244384E984126FC3CB4F544ADE8E@us01wembx1.internal.synopsys.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi,=0A=
=0A=
On 9/10/2018 1:13 PM, Thinh Nguyen wrote:=0A=
> Hi Anurag,=0A=
>=0A=
> On 9/8/2018 8:03 AM, Anurag Kumar Vulisha wrote:=0A=
>> For stream capable endpoints, uas layer can queue mulpile requests on=0A=
>> single ep with different stream ids. So, there can be multiple pending=
=0A=
>> requests waiting to be transferred. This patch changes the code to check=
=0A=
>> for any pending requests waiting to be transferred on ep started_list an=
d=0A=
>> calls __dwc3_gadget_kick_transfer() if any.=0A=
> Whenever a function driver queues a request, then=0A=
> __dwc3_gadget_kick_transfer() will be called right? What case exactly is=
=0A=
> this for? Scatter gathering? If so, then we probably need further=0A=
> explanation. (e.g. Why wait to call __dwc3_gadget_kick_transfer() on=0A=
> XferComplete event rather than sending a START_TRANSFER command for=0A=
> every prepared TRB whenever we do __dwc3_gadget_kick_transfer()?).=0A=
=0A=
Please ignore my question.  We only do 1 transfer per stream id at a=0A=
time. That's fine.=0A=
=0A=
Thanks,=0A=
Thinh=0A=