Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1755454AbcJGHnC (ORCPT <rfc822;w@1wt.eu>);
        Fri, 7 Oct 2016 03:43:02 -0400
Received: from mga05.intel.com ([192.55.52.43]:61685 "EHLO mga05.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752581AbcJGHmx (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 7 Oct 2016 03:42:53 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.31,308,1473145200"; 
   d="asc'?scan'208";a="17143250"
From: Felipe Balbi <balbi@kernel.org>
To: Michael =?utf-8?Q?Niew=C3=B6hner?= <linux@mniewoehner.de>,
        Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
        Pankaj Dubey <pankaj.dubey@samsung.com>,
        Anand Moon <linux.amoon@gmail.com>,
        Mathias Nyman <mathias.nyman@linux.intel.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Kukjin Kim <kgene@kernel.org>,
        Krzysztof Kozlowski <k.kozlowski@samsung.com>,
        Linux USB Mailing List <linux-usb@vger.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
        "linux-samsung-soc\@vger.kernel.org" 
        <linux-samsung-soc@vger.kernel.org>,
        Linux Kernel <linux-kernel@vger.kernel.org>,
        Vivek Gautam <gautam.vivek@samsung.com>,
        Alim Akhtar <alim.akhtar@samsung.com>,
        Pankaj Dubey <pankaj.dubey@samsung.com>
Subject: Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422
In-Reply-To: <1475771380.22019.5.camel@mniewoehner.de>
References: <1472414695.3845.3.camel@mniewoehner.de> <87lgzgdof3.fsf@linux.intel.com> <57C41582.1030604@linux.intel.com> <1472468730.4925.3.camel@mniewoehner.de> <CANAwSgQMsK8YPxR==UXtR49kiJzYhkzvSCNwn8mDJfj-3wpa2w@mail.gmail.com> <CAFp+6iGrS0DTP=KUKDvk3NwWB32+1uj-irKT6fn5XTcfk572Hg@mail.gmail.com> <1475578687.1912.28.camel@mniewoehner.de> <CAFp+6iGx-jf+xrdHF=0J3FK9dDBg54zESYNVo8bz2Qz6G4gEZg@mail.gmail.com> <1475771380.22019.5.camel@mniewoehner.de>
Date: Fri, 07 Oct 2016 10:42:21 +0300
Message-ID: <87y420wqoy.fsf@linux.intel.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
        micalg=pgp-sha256; protocol="application/pgp-signature"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1564
Lines: 44

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi,

Michael Niew=C3=B6hner <linux@mniewoehner.de> writes:
>> The clocks are same across working/non-working.
>> Is it possible to bisect the commit that's causing hang for 4.8x ?
>
>
> [c499ff71ff2a281366c6ec7a904c547d806cbcd1] usb: dwc3: core: re-factor ini=
t and exit paths
> This patch causes both the hang on reboot and the lsusb hang.

How to reproduce? Why don't we see this on x86 and TI boards? I'm
guessing this is failed bisection, as I can't see anything in that
commit that would cause reboot hang. Also, that code path is *NOT*
executed when you run lsusb.

=2D-=20
balbi

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJX91HdAAoJEMy+uJnhGpkGfAAQAMZCENtAX0a9lufBr3mIPf3q
ohYC5aYGSvfTgamFu0JZQneHAaFA+2GBOjpotm2mFOBxZ/IijKChHYmU9P1zLRLp
PbOimkQ3gI+UU4kfZR0fb+sZ40htSODfm5L6KuzlDWGR35Vb+v0ymJ2b3Ga4CRC1
XYOebcEvIXpvTJ1T3HvuLy7DWObdZx4c0NdfTM/Wahyglvd8/hV7c1CWjsvECCyA
b93Nxlo+zxENyc8/JNE5qbJfeDhIqFqj1bIUm2jgIBDZSNSHdxViBWEjGjH/lck5
8wAMlvDpTbte7hdbVdbxx6Ca5HeeNv9gG+Odto0y3x0zPU7samFjevIfsz2jlL9G
m2TfRgyisJlRQRS58DLNibdvPlaOHCiZ4K58CB2dQ1H4tvBofW61SOWR8JowhEap
5VhaJmhOhLXR75QmDQujl3ZbOKwTPqftRanlQkU/qgvzb7WyXRjfzUmPrh+XoXxp
UX+z+7xKXtas/FwZsw9CUnQODfmMfPpFceWUwOpj+o5LCPGqE5Du+/zQjLSnU6Ir
h7Skq8nEKC0R5OXQbgTiISlx7FnOKGBs4oJO1/Zsq46hN4rCrqpigF17pssozPCY
XFGB4IEj7dVv/hoAnvDnPxMWhztoI9FuBY8e7HFAXHn5WWvevT8APuHYQo0iT9ym
C0J84vq7dDSvMre0Xh8z
=wVuZ
-----END PGP SIGNATURE-----
--=-=-=--