From: Doug Anderson <dianders@chromium.org>
To: Karl Palsson <karlp@tweak.net.au>
Cc: Heiko Stuebner <heiko@sntech.de>,
Julius Werner <jwerner@chromium.org>,
Felipe Balbi <balbi@kernel.org>,
"caesar.upstream@gmail.com" <caesar.upstream@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"huangtao@rock-chips.com" <huangtao@rock-chips.com>,
"johnyoun@synopsys.com" <johnyoun@synopsys.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
"linux@mniewoehner.de" <linux@mniewoehner.de>,
"repk@triplefau.lt" <repk@triplefau.lt>,
"stefan.wahren@i2se.com" <stefan.wahren@i2se.com>
Subject: Re: [RFT PATCH 1/2] usb: dwc2: Add a 10 ms delay to dwc2_core_reset()
Date: Fri, 4 Mar 2016 16:36:31 -0800 [thread overview]
Message-ID: <CAD=FV=XOiKJgadqOkTG3qW7AxgmBbvSLMNh9Fp+KL0ZeKXsBUg@mail.gmail.com> (raw)
In-Reply-To: <20160304234507-549-39315-mailpile@palmtree-beeroclock-net>
Hi,
On Fri, Mar 4, 2016 at 3:46 PM, Karl Palsson <karlp@tweak.net.au> wrote:
>> + /*
>> + * Sleep for 10-15 ms after the reset to let it finish.
>> + *
>> + * It's been confirmed on at least one version of the controller
>> + * that this is a requirement that this is a requirement in order for
>
> ^^ duplicate wording here.
Thanks for catching. I'm happy to re-post with fixed wording or have
a maintainer adjust it to this if/when it is applied:
* It's been confirmed on at least one version of the
* controller that this is a requirement in order for
* everything to settle. Specifically if you:
Please let me know if you'd like it re-posted.
-Doug
next prev parent reply other threads:[~2016-03-05 0:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 18:23 [RFT PATCH 1/2] usb: dwc2: Add a 10 ms delay to dwc2_core_reset() Douglas Anderson
2016-03-04 18:23 ` [RFT PATCH 2/2] Revert "usb: dwc2: Fix probe problem on bcm2835" Douglas Anderson
2016-03-04 22:54 ` Michael Niewoehner
2016-03-07 18:40 ` Stefan Wahren
2016-03-07 21:30 ` Doug Anderson
2016-03-08 17:49 ` Stefan Wahren
2016-03-09 19:01 ` Stefan Wahren
2016-03-09 19:06 ` Doug Anderson
2016-03-10 19:14 ` John Youn
2016-03-16 18:28 ` John Youn
2016-03-18 23:14 ` Stefan Wahren
2016-03-19 2:17 ` Eric Anholt
2016-03-19 7:44 ` Martin Sperl
2016-03-19 9:52 ` Stefan Wahren
2016-03-19 10:10 ` Martin Sperl
2016-03-19 12:09 ` Stefan Wahren
2016-03-19 9:45 ` Stefan Wahren
2016-03-19 5:21 ` Doug Anderson
2016-03-22 19:26 ` John Youn
2016-03-22 19:44 ` Doug Anderson
2016-03-22 20:37 ` John Youn
2016-03-24 6:18 ` John Youn
2016-03-04 22:54 ` [RFT PATCH 1/2] usb: dwc2: Add a 10 ms delay to dwc2_core_reset() Michael Niewoehner
2016-03-05 0:09 ` Michael Niewoehner
2016-03-05 0:33 ` Doug Anderson
2016-03-05 1:09 ` Doug Anderson
2016-03-05 20:41 ` Michael Niewoehner
2016-03-06 1:38 ` Doug Anderson
2016-03-04 23:46 ` Karl Palsson
2016-03-05 0:36 ` Doug Anderson [this message]
2016-03-04 23:52 ` Sergei Shtylyov
2016-03-05 2:23 ` John Youn
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='CAD=FV=XOiKJgadqOkTG3qW7AxgmBbvSLMNh9Fp+KL0ZeKXsBUg@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=balbi@kernel.org \
--cc=caesar.upstream@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=johnyoun@synopsys.com \
--cc=jwerner@chromium.org \
--cc=karlp@tweak.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@mniewoehner.de \
--cc=repk@triplefau.lt \
--cc=stefan.wahren@i2se.com \
/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).