Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753864AbcCSJxO (ORCPT ); Sat, 19 Mar 2016 05:53:14 -0400 Received: from mout.kundenserver.de ([212.227.126.135]:50687 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753436AbcCSJxF convert rfc822-to-8bit (ORCPT ); Sat, 19 Mar 2016 05:53:05 -0400 Date: Sat, 19 Mar 2016 10:52:38 +0100 (CET) From: Stefan Wahren To: Martin Sperl , Eric Anholt Cc: Michael Niewoehner , Tao Huang , John Youn , Julius Werner , Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" , "linux-usb@vger.kernel.org" , Caesar Wang , Doug Anderson , Heiko Stuebner , Felipe Balbi , Remi Pommarel Message-ID: <376411469.89406.35996342-72cd-48a5-8893-944da9f8a599.open-xchange@email.1und1.de> In-Reply-To: <8E14A795-8C35-4C4D-8D3A-09F29EE42A5F@martin.sperl.org> References: <1457115786-11370-1-git-send-email-dianders@chromium.org> <1457115786-11370-2-git-send-email-dianders@chromium.org> <1400647253.149212.b3bb45b6-c852-4cf1-9d3e-9fb299176369.open-xchange@email.1und1.de> <941828343.8833.cdbd40c7-e6f4-4b3e-9665-30fc6680f6e0.open-xchange@email.1und1.de> <56E1C79D.3090104@synopsys.com> <56E9A5E8.7090102@synopsys.com> <1440674775.86542.7bdab192-0ed1-49f2-8559-819af7131cbd.open-xchange@email.1und1.de> <87fuvn1a9p.fsf@eliezer.anholt.net> <8E14A795-8C35-4C4D-8D3A-09F29EE42A5F@martin.sperl.org> Subject: Re: [RFT PATCH 2/2] Revert "usb: dwc2: Fix probe problem on bcm2835" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-Priority: 3 Importance: Medium X-Mailer: Open-Xchange Mailer v7.8.0-Rev26 X-Originating-Client: com.openexchange.ox.gui.dhtml X-Provags-ID: V03:K0:hTy8sDZ97ymnmkN7ZPZlWIFvCcZ/zEtdOrjyM4BYuagua2GprUV NPp9upLczTTaY99LOgSC53eONqrNjOm5JJNaxbGAakdVZntE73vcjLd3mcqoCMxObrG4C8b JstBUDJ4fX68uvRG1b7uxLBzRZLzd+26ZAa3XFMLnwPI5tl2GQNZvyXTT17U7ct9+aO9lyE uDkK3z3F5VZQbr8JIBvkA== X-UI-Out-Filterresults: notjunk:1;V01:K0:GX0O1Zhym+g=:n3OYL1pIU9ydAEqDLWNLI7 VIU/K151Qwxi04JzNMkFjPa2NnNewdH14cY0B7RfFHXKx1IXueSvTv8s3H4YjMQCeVFAFJYzI 5KC5p2hxu/GT1ys7fja4Cwq/PslrZQ9AFYj9YJXTTK1jPIPbhemfEAKIk2FzCFXzhlckhDwaD XLDGR3ln17E7XQDCnELYjh5m4JOgAPhFTahtvYLBXAZpWVpZvO0uuVQhsgxOBrKAIdisLpqRS h8DrDZnKo9uS+unHdW/duyOK0MeTNzGd/vxHvEYbFSOhWVCK79Ttyb47JhBreICOpE8AMmpj2 +MShyVidG2Ol1lNNa5QZtGh4gWq6TY4MDTsorREv6I6F2a3byb7mh29bOch8Jh9CxRiudNnK9 w8C5j1GzW1GmolKbl/FoltiMFZGFjkQ0L9nQfisTnI8cgc+bZaW6hIiQzyI6qQlbAVh/vtZ22 QN6wvgdgagf1igv++ovxdbhzw/y3jNnKvvuC15JK7ZKeLi+Qt4px2eL5A3p5kL/GCWT1bemL2 kQTtngkUFzS/aeoHeYiJ2am842o6sgag99MXbgvHxVf11s8Yf+KBbcWXUQGJ4cXls6hTn/g7Q C3Wc7PEWo5VHw7YmWvsXVZ4/07y8l0Nlcn9NZZhMGFRgV48lzVO5tl3XITh3vLAvOtLa5nznI rtzbq/mp0gHY9deC5pqgirVdKQvCy/2PN5C1dn6tfv7g69e4W+ZLglqSuS5tZojVagX+wqcRU XtlLJlSBlFq9L1gb Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1537 Lines: 52 Hi, > Martin Sperl hat am 19. März 2016 um 08:44 > geschrieben: > > > > > On 19.03.2016, at 03:17, Eric Anholt wrote: > > > > Stefan Wahren writes: > > > >> Hi Eric, > >> hi Martin, > >> > >>> John Youn hat am 16. März 2016 um 19:28 > >>> geschrieben: > >>> > >>> > >>> On 3/10/2016 11:14 AM, John Youn wrote: > >>>> On 3/9/2016 11:06 AM, Doug Anderson wrote: > >>>>> > >>>>> John: it's pretty clear that there's something taking almost exactly > >>>>> 10ms on my system and almost exactly 50ms on Stefan's system. Is > >>>>> there some register we could poll to see when this process is done? > >>>>> ...or can we look at the dwc2 revision number / feature register and > >>>>> detect how long to delay? > >>>>> > > Maybe this difference is related to overclocking settings in the firmware? > > >>> > >>> 1. What is the AHB Clock frequency? Is the AHB Clock gated during > >>> Reset? > > > > Low confidence here as I'm tracing lines across a ton of modules, but it > > looks like it comes from the USB AXI clock in peri_image, which is a > > gate on the normal 250Mhz APB clock, but nothing should be touching that > > gate register as part of USB reset as far as I know. > > > Isn’t it possible that this clock (probably BCM2835_CLOCK_VPU) is > changed by the firmware due to overclocking settings in /boot/config.txt? i don't use any overclocking settings. Are you able to reproduce the behavior on your Pi? Stefan > > Martin > >