mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: John Youn <johnyoun@synopsys.com>,
	linux-usb@vger.kernel.org, Doug Anderson <dianders@chromium.org>
Cc: Felipe Balbi <balbi@ti.com>,
	Michael Niewoehner <linux@mniewoehner.de>,
	Tao Huang <huangtao@rock-chips.com>,
	Julius Werner <jwerner@chromium.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org,
	Caesar Wang <caesar.upstream@gmail.com>,
	Heiko Stuebner <heiko@sntech.de>, Felipe Balbi <balbi@kernel.org>,
	Remi Pommarel <repk@triplefau.lt>,
	Kever Yang <kever.yang@rock-chips.com>,
	Przemek Rudy <prudy1@o2.pl>
Subject: Re: [RFT PATCH 0/4] usb: dwc2: Fix core reset and force mode delay problems
Date: Thu, 31 Mar 2016 10:52:55 +0200	[thread overview]
Message-ID: <56FCE567.1050004@i2se.com> (raw)
In-Reply-To: <cover.1459211397.git.johnyoun@synopsys.com>

Hi John,

Am 29.03.2016 um 04:36 schrieb John Youn:
> Hi,
>
> The following patch series addresses the core reset and force mode
> delay problems we have been seeing on dwc2 for some platforms.
>
> I think I have identified the source of the inconsistencies between
> platforms and this series attempts to address them.
>
> Basically everything stems from the IDDIG debounce filter delay, which
> is a function of the PHY clock speed and can range from 5-50 ms if
> enabled. This delay must be taken into account on core reset and force
> modes. A full explanation is provided in the patch commit log and code
> comments.
>
> The first two patches are prerequisites to the force mode fixes,
> including one patch that was sent separately by Przemek Rudy. I have
> resubmitted it with this series for convenience.
>
> Please help by reviewing and testing on your platforms.
>
> Patches were tested on:
> * Synopsys HAPS platform IP 3.20a OTG, dr_mode=OTG,HOST,PERIPHERAL

i applied the complete patch series on 4.6rc-1 and successfully tested
it with my Raspberry Pi B (IP 2.80a, dr_mode=HOST).

Probing and usual USB devices (network, keyboard) still works fine.

Do you need any other specific tests?

Regards
Stefan


>
> Regards,
> John
>
> John Youn (3):
>   usb: dwc2: gadget: Only initialize device if in device mode
>   usb: dwc2: Add delay to core soft reset
>   usb: dwc2: Properly account for the force mode delays
>
> Przemek Rudy (1):
>   usb: dwc2: do not override forced dr_mode in gadget setup
>
>  drivers/usb/dwc2/core.c     | 195 ++++++++++++++++++++++++++++----------------
>  drivers/usb/dwc2/core.h     |   2 +-
>  drivers/usb/dwc2/gadget.c   |  30 +++++--
>  drivers/usb/dwc2/hcd.c      |   6 +-
>  drivers/usb/dwc2/hw.h       |   1 +
>  drivers/usb/dwc2/platform.c |   9 +-
>  6 files changed, 161 insertions(+), 82 deletions(-)
>

  parent reply	other threads:[~2016-03-31  8:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29  2:36 John Youn
2016-03-29  2:36 ` [RFT PATCH 1/4] usb: dwc2: do not override forced dr_mode in gadget setup John Youn
2016-03-29  2:36 ` [RFT PATCH 2/4] usb: dwc2: gadget: Only initialize device if in device mode John Youn
2016-03-29  2:36 ` [RFT PATCH 3/4] usb: dwc2: Add delay to core soft reset John Youn
2016-03-29  2:36 ` [RFT PATCH 4/4] usb: dwc2: Properly account for the force mode delays John Youn
2016-03-31  8:52 ` Stefan Wahren [this message]
2016-03-31 20:45 ` [RFT PATCH 0/4] usb: dwc2: Fix core reset and force mode delay problems Michael Niewoehner
2016-03-31 21:43 ` Michael Niewoehner
2016-04-07 18:41   ` John Youn
2016-04-07 20:36     ` Michael Niewoehner
2016-04-07 22:12       ` John Youn
2016-04-08 10:25         ` Michael Niewoehner

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=56FCE567.1050004@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=balbi@kernel.org \
    --cc=balbi@ti.com \
    --cc=caesar.upstream@gmail.com \
    --cc=dianders@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=johnyoun@synopsys.com \
    --cc=jwerner@chromium.org \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@mniewoehner.de \
    --cc=prudy1@o2.pl \
    --cc=repk@triplefau.lt \
    /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

Powered by JetHome