From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"felipe.balbi@linux.intel.com" <felipe.balbi@linux.intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-stable <stable@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc2: use a longer AHB idle timeout in dwc2_core_reset()
Date: Mon, 1 Jul 2019 19:54:15 +0200 [thread overview]
Message-ID: <CAFBinCDDyG_CxW+PB_OrUXfy-aDKSoewC2OyCfGh18N=omSgcQ@mail.gmail.com> (raw)
In-Reply-To: <a7647aea-b3e6-b785-8476-1851f50beff1@synopsys.com>
On Mon, Jun 24, 2019 at 7:41 AM Minas Harutyunyan
<Minas.Harutyunyan@synopsys.com> wrote:
>
> On 6/20/2019 9:51 PM, Martin Blumenstingl wrote:
> > Use a 10000us AHB idle timeout in dwc2_core_reset() and make it
> > consistent with the other "wait for AHB master IDLE state" ocurrences.
> >
> > This fixes a problem for me where dwc2 would not want to initialize when
> > updating to 4.19 on a MIPS Lantiq VRX200 SoC. dwc2 worked fine with
> > 4.14.
> > Testing on my board shows that it takes 180us until AHB master IDLE
> > state is signalled. The very old vendor driver for this SoC (ifxhcd)
> > used a 1 second timeout.
> > Use the same timeout that is used everywhere when polling for
> > GRSTCTL_AHBIDLE instead of using a timeout that "works for one board"
> > (180us in my case) to have consistent behavior across the dwc2 driver.
> >
> > Cc: linux-stable <stable@vger.kernel.org> # 4.19+
> > Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> > ---
>
> Acked-by: Minas Harutyunyan <hminas@synopsys.com>
thank you for reviewing this!
is there any chance we can get this fix into Linux 5.3? I know that
it's too late for 5.2 so I'm fine with skipping that.
Martin
next prev parent reply other threads:[~2019-07-01 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 17:50 [PATCH] usb: dwc2: use a longer AHB idle timeout in dwc2_core_reset() Martin Blumenstingl
2019-06-24 5:41 ` Minas Harutyunyan
2019-07-01 17:54 ` Martin Blumenstingl [this message]
2019-07-03 9:01 ` Martin Blumenstingl
2019-07-03 11:38 ` Felipe Balbi
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='CAFBinCDDyG_CxW+PB_OrUXfy-aDKSoewC2OyCfGh18N=omSgcQ@mail.gmail.com' \
--to=martin.blumenstingl@googlemail.com \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@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).