From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Felipe Balbi <balbi@kernel.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: John Youn <John.Youn@synopsys.com>
Subject: Re: [PATCH 2/2] usb: dwc3: gadget: Handle DEV_TXF_FLUSH_BYPASS capability
Date: Mon, 26 Apr 2021 21:27:08 +0000 [thread overview]
Message-ID: <15c8cc72-0b74-d909-5149-13c71d7f577f@synopsys.com> (raw)
In-Reply-To: <874kfxmszt.fsf@kernel.org>
Felipe Balbi wrote:
> Thinh Nguyen <Thinh.Nguyen@synopsys.com> writes:
>
>> DWC_usb32 IP introduces a new behavior when handling NoStream event for
>> IN endpoints. If the controller is capable of DEV_TXF_FLUSH_BYPASS, then
>> the driver does not need to force to restart stream for IN endpoints.
>> The controller will generate ERDY and restart the stream periodically.
>>
>> Signed-off-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
>
> so we still need to force restart for RX? Just making sure. Other than
> that:
>
> Acked-by: Felipe Balbi <balbi@kernel.org>
>
Yes, it's only for Tx. Same behavior remains for Rx. We have some
updates to simplify our design handling Tx direction.
Thanks,
Thinh
prev parent reply other threads:[~2021-04-26 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 23:51 [PATCH 0/2] usb: dwc3: gadget: Check new capability Thinh Nguyen
2021-04-22 23:51 ` [PATCH 1/2] usb: dwc3: Capture new capability register GHWPARAMS9 Thinh Nguyen
2021-04-23 6:08 ` Felipe Balbi
2021-04-22 23:51 ` [PATCH 2/2] usb: dwc3: gadget: Handle DEV_TXF_FLUSH_BYPASS capability Thinh Nguyen
2021-04-23 6:09 ` Felipe Balbi
2021-04-26 21:27 ` Thinh Nguyen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15c8cc72-0b74-d909-5149-13c71d7f577f@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).