From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 42D33C43144 for ; Fri, 22 Jun 2018 16:27:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EF865245C5 for ; Fri, 22 Jun 2018 16:27:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="UDMHGNIr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EF865245C5 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934375AbeFVQ1X (ORCPT ); Fri, 22 Jun 2018 12:27:23 -0400 Received: from mail-ot0-f194.google.com ([74.125.82.194]:43648 "EHLO mail-ot0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934061AbeFVQ1V (ORCPT ); Fri, 22 Jun 2018 12:27:21 -0400 Received: by mail-ot0-f194.google.com with SMTP id i19-v6so8113219otk.10; Fri, 22 Jun 2018 09:27:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YTOwI7XkivqFS60t2cdtXzjta4Bc+H3Zs08Fazh57p0=; b=UDMHGNIrYp1MkrjsS0wumYWKBHEMV5BcLeZyIj9elNOANl7xipVb3zriLY/CmyCufW 0L54SCr2GSjKg8szTOufFi93DRe75ajErOkkGACtO/p3ppso07uNwa7gtsigBy/0DBoZ fpdCrJ6zYNCJe8OcMHdOk+8Y3wszEdeoKGyML1nInpFaqDQdkU2R+/6J/lOsqldIgu+f +UlHr2WIjJhxyKyDQwOUufFajSnP5yEDr3RHfEVyKGMRvLMGaMJn3F4LyovYCCzrW175 AME2t86La+kaWlhkGXESzGukBYDaLltnvT1uFazUZntQlYY4f79MQvS5Y3dMTZ+Cuha+ fiCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YTOwI7XkivqFS60t2cdtXzjta4Bc+H3Zs08Fazh57p0=; b=r01FpN7v2cvM8RYy3EHC2ZlSGTex0n441TByjvMZAPCwmC4eQUdLyyRFTWI/Mffjdq m39752eQBRnBo0mk5htRmQNVMHzn2kdoxSMI3zT9KDtXQqLrcDPF3IA7BGdHsi1wqM0A FKsn4B0/Frx9fuY/w4pxHN/2egz6hsbnSgxEnA09gl1xf5P/TVKzFMiC0XQObIXo5N0v kzBpme8eAZ3QSxWGV3i6u79T1sCxFfFnU7R0Y3FU2n47rIyx/jjyB23QIH55K82hF55f VrHq+y4rWyLdC1yXHyodMy09BpQ6UbO18CM1c1AvYtdD43gPrNaW18Okgy1vm6Z14u07 +Aug== X-Gm-Message-State: APt69E1fg43Lhah/NN4FHMoM3RRcjsREeFJIrKP6QtGQU5vBwe8ixkD8 08VoRdsow2RFPhrYrxlYtuxG/RooZu4WvoNGQRI= X-Google-Smtp-Source: ADUXVKIXzJtWu2oDfuSbtTHmnRGY3lM6gA9riJuzMBI+joYO2rCaYeO5+DHpKpRxg1FJZwyETGpH68Cr6qjSm3wY8MY= X-Received: by 2002:a9d:62d3:: with SMTP id z19-v6mr1244853otk.159.1529684840764; Fri, 22 Jun 2018 09:27:20 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:1049:0:0:0:0:0 with HTTP; Fri, 22 Jun 2018 09:27:20 -0700 (PDT) In-Reply-To: References: <20180530173414.6121-1-andrew.smirnov@gmail.com> From: Fabio Estevam Date: Fri, 22 Jun 2018 13:27:20 -0300 Message-ID: Subject: Re: [PATCH] usb: chipidea: Fix ULPI on imx51 To: Andrey Smirnov Cc: Greg Kroah-Hartman , Nikita Yushchenko , Peter Chen , USB list , linux-kernel , linux-arm-kernel , Fabio Estevam , Chris Healy , Lucas Stach , Sebastian Reichel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Andrey, On Thu, Jun 21, 2018 at 6:44 PM, Andrey Smirnov wrote: > I just finished experimenting with it on RDU1 and Babbage boards and I > can't reproduce the hang that you describe against 4.18-rc1. At this > point I wonder if it's the bootloader that is a variable that plays > into this. I was booting both boards with 2018.06.0 version of barebox > + the custom patches that can be found here > https://github.com/ndreys/barebox/commits/rdu1-netboot. Note that the > last patch in that branch/stack was added as a part of this > investigation, but even before it, I was able to boot Linux just fine, > albeit without working USB. Thanks for investigating this issue. Yes, t is possible that the difference in behaviour that we see could be related to the fact we use different bootloaders. In order to make things easier, I am sharing a Buildroot image for imx51-babbage that contains U-Boot 2018.05 + kernel 4.17.2: https://www.dropbox.com/s/yevnu4y1zdchnbt/sdcard.img?dl=0 Please flash it directly to the SD card via dd and boot it. You will notice that it will boot normally. Then please copy a 4.18-rc1 zImage into the first SD card partition and you will notice the hang. Thanks From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Subject: usb: chipidea: Fix ULPI on imx51 From: Fabio Estevam Message-Id: Date: Fri, 22 Jun 2018 13:27:20 -0300 To: Andrey Smirnov Cc: Greg Kroah-Hartman , Nikita Yushchenko , Peter Chen , USB list , linux-kernel , linux-arm-kernel , Fabio Estevam , Chris Healy , Lucas Stach , Sebastian Reichel List-ID: SGkgQW5kcmV5LAoKT24gVGh1LCBKdW4gMjEsIDIwMTggYXQgNjo0NCBQTSwgQW5kcmV5IFNtaXJu b3YKPGFuZHJldy5zbWlybm92QGdtYWlsLmNvbT4gd3JvdGU6Cgo+IEkganVzdCBmaW5pc2hlZCBl eHBlcmltZW50aW5nIHdpdGggaXQgb24gUkRVMSBhbmQgQmFiYmFnZSBib2FyZHMgYW5kIEkKPiBj YW4ndCByZXByb2R1Y2UgdGhlIGhhbmcgdGhhdCB5b3UgZGVzY3JpYmUgYWdhaW5zdCA0LjE4LXJj MS4gQXQgdGhpcwo+IHBvaW50IEkgd29uZGVyIGlmIGl0J3MgdGhlIGJvb3Rsb2FkZXIgdGhhdCBp cyBhIHZhcmlhYmxlIHRoYXQgcGxheXMKPiBpbnRvIHRoaXMuIEkgd2FzIGJvb3RpbmcgYm90aCBi b2FyZHMgd2l0aCAyMDE4LjA2LjAgdmVyc2lvbiBvZiBiYXJlYm94Cj4gKyB0aGUgY3VzdG9tIHBh dGNoZXMgdGhhdCBjYW4gYmUgZm91bmQgaGVyZQo+IGh0dHBzOi8vZ2l0aHViLmNvbS9uZHJleXMv YmFyZWJveC9jb21taXRzL3JkdTEtbmV0Ym9vdC4gTm90ZSB0aGF0IHRoZQo+IGxhc3QgcGF0Y2gg aW4gdGhhdCBicmFuY2gvc3RhY2sgd2FzIGFkZGVkIGFzIGEgcGFydCBvZiB0aGlzCj4gaW52ZXN0 aWdhdGlvbiwgYnV0IGV2ZW4gYmVmb3JlIGl0LCBJIHdhcyBhYmxlIHRvIGJvb3QgTGludXgganVz dCBmaW5lLAo+IGFsYmVpdCB3aXRob3V0IHdvcmtpbmcgVVNCLgoKVGhhbmtzIGZvciBpbnZlc3Rp Z2F0aW5nIHRoaXMgaXNzdWUuCgpZZXMsIHQgaXMgcG9zc2libGUgdGhhdCB0aGUgZGlmZmVyZW5j ZSBpbiBiZWhhdmlvdXIgdGhhdCB3ZSBzZWUgY291bGQKYmUgcmVsYXRlZCB0byB0aGUgZmFjdCB3 ZSB1c2UgZGlmZmVyZW50IGJvb3Rsb2FkZXJzLgoKSW4gb3JkZXIgdG8gbWFrZSB0aGluZ3MgZWFz aWVyLCBJIGFtIHNoYXJpbmcgYSBCdWlsZHJvb3QgaW1hZ2UgZm9yCmlteDUxLWJhYmJhZ2UgdGhh dCBjb250YWlucyBVLUJvb3QgMjAxOC4wNSArIGtlcm5lbCA0LjE3LjI6Cmh0dHBzOi8vd3d3LmRy b3Bib3guY29tL3MveWV2bnU0eTF6ZGNobmJ0L3NkY2FyZC5pbWc/ZGw9MAoKUGxlYXNlIGZsYXNo IGl0IGRpcmVjdGx5IHRvIHRoZSBTRCBjYXJkIHZpYSBkZCBhbmQgYm9vdCBpdC4KCllvdSB3aWxs IG5vdGljZSB0aGF0IGl0IHdpbGwgYm9vdCBub3JtYWxseS4gVGhlbiBwbGVhc2UgY29weSBhCjQu MTgtcmMxIHpJbWFnZSBpbnRvIHRoZSBmaXJzdCBTRCBjYXJkIHBhcnRpdGlvbiBhbmQgeW91IHdp bGwgbm90aWNlCnRoZSBoYW5nLgoKVGhhbmtzCi0tLQpUbyB1bnN1YnNjcmliZSBmcm9tIHRoaXMg bGlzdDogc2VuZCB0aGUgbGluZSAidW5zdWJzY3JpYmUgbGludXgtdXNiIiBpbgp0aGUgYm9keSBv ZiBhIG1lc3NhZ2UgdG8gbWFqb3Jkb21vQHZnZXIua2VybmVsLm9yZwpNb3JlIG1ham9yZG9tbyBp bmZvIGF0ICBodHRwOi8vdmdlci5rZXJuZWwub3JnL21ham9yZG9tby1pbmZvLmh0bWwK From mboxrd@z Thu Jan 1 00:00:00 1970 From: festevam@gmail.com (Fabio Estevam) Date: Fri, 22 Jun 2018 13:27:20 -0300 Subject: [PATCH] usb: chipidea: Fix ULPI on imx51 In-Reply-To: References: <20180530173414.6121-1-andrew.smirnov@gmail.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Andrey, On Thu, Jun 21, 2018 at 6:44 PM, Andrey Smirnov wrote: > I just finished experimenting with it on RDU1 and Babbage boards and I > can't reproduce the hang that you describe against 4.18-rc1. At this > point I wonder if it's the bootloader that is a variable that plays > into this. I was booting both boards with 2018.06.0 version of barebox > + the custom patches that can be found here > https://github.com/ndreys/barebox/commits/rdu1-netboot. Note that the > last patch in that branch/stack was added as a part of this > investigation, but even before it, I was able to boot Linux just fine, > albeit without working USB. Thanks for investigating this issue. Yes, t is possible that the difference in behaviour that we see could be related to the fact we use different bootloaders. In order to make things easier, I am sharing a Buildroot image for imx51-babbage that contains U-Boot 2018.05 + kernel 4.17.2: https://www.dropbox.com/s/yevnu4y1zdchnbt/sdcard.img?dl=0 Please flash it directly to the SD card via dd and boot it. You will notice that it will boot normally. Then please copy a 4.18-rc1 zImage into the first SD card partition and you will notice the hang. Thanks