Received: by 10.192.165.156 with SMTP id m28csp1576886imm; Wed, 18 Apr 2018 11:57:44 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+pqt+Thwj9WubijovRs8MHBVHfxJNYyK3WbPTemjhmNvERq42QZ8WYCW6+FupLFdlOAKQv X-Received: by 10.101.76.129 with SMTP id m1mr2598290pgt.90.1524077864897; Wed, 18 Apr 2018 11:57:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524077864; cv=none; d=google.com; s=arc-20160816; b=xmEGSeUNALH0EYYlJ/nJmuu/44Gv424pD7toYBB7/96GDuwZj3TmmA+Fb7GXWlOwAr 5+OLcdHnBpVP10djQlTqp3K8WuifgJ5NM9emefDu+9YdMZrTjSwQbJ7KLV749GhQ09JH 5JjaiSatuCSDuCujEHabQzSA20CO1RG4cCVPIdHa2X0REHNUk1nQjpcHKhl5EcqHCpbk U3pGJEwHVu0ad9pTRs0p4Qc51+RVw7s6hVzpxK+yvouxSPFgwKIE9jQkeqNjTt3mDcYe Eehd3VyKyNqoVjfVeHSLLIz4jsifjyzqEVsZjuI1sP0BUIPiCFlOOUSk2VBkzyALGPrT Dd7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=zb2eJuinOcMXOoMuBawv7ARlWIurOCeeh4/QG4iq/Qs=; b=B7krGsDcIzBg5uzsxys9W2NlGYzBzRcbqpObkgdNZ9ArDR5fBtJG9r6OZl425RFX2T bLzffdHqpEbAqUfDIS+RNbOkxPOelkjZU6tc0EVycaqYAFtU5cpKaaXRr6IT5I1hgjmv 8oOXBvqQoKczPoYex7qjpXkmQaiookZYB79bMYYH0rdb9IDRI6pdv2CXMrQi3oVlBr8q z4CP8E6ZTOoqBQv3TJ0XO0Es3SmhKYeJepbPT3+isxVm7+G5cUDpWOn5fTOFEaRoWzhX LuAVZuTk8ERECRB5t4flgSR0wN6mDfDVrsMm6rM7XuRLuIps9EJ5JCnRjy2ip83Xn0pB jIlA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=Nqj1K6ef; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z3si1556273pfe.255.2018.04.18.11.57.31; Wed, 18 Apr 2018 11:57:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=Nqj1K6ef; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752702AbeDRS4Y (ORCPT + 99 others); Wed, 18 Apr 2018 14:56:24 -0400 Received: from lelnx193.ext.ti.com ([198.47.27.77]:65375 "EHLO lelnx193.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750872AbeDRS4W (ORCPT ); Wed, 18 Apr 2018 14:56:22 -0400 Received: from dflxv15.itg.ti.com ([128.247.5.124]) by lelnx193.ext.ti.com (8.15.1/8.15.1) with ESMTP id w3IIuDYS019259; Wed, 18 Apr 2018 13:56:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ti.com; s=ti-com-17Q1; t=1524077774; bh=X0afdeZNylN4Y4Fvx3VsE7lQ8lM98ZyYFANu0crO4l4=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=Nqj1K6efqrgNYsg619zVMXzgtjldQ1Suf2375f5dYmp7EtemfJFcWB1aov/lsdAco WyEY++w6QhcF//DETj1n5citPbRVP0Dr5xLAb5/2ix73J4509H+1t7A8J3/7tSbY2B aWITxpEHLspsSSLmTQgosKCWKWB/x6jzZ9hu8X6k= Received: from DFLE101.ent.ti.com (dfle101.ent.ti.com [10.64.6.22]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id w3IIuDww007397; Wed, 18 Apr 2018 13:56:13 -0500 Received: from DFLE101.ent.ti.com (10.64.6.22) by DFLE101.ent.ti.com (10.64.6.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.35; Wed, 18 Apr 2018 13:56:13 -0500 Received: from dflp32.itg.ti.com (10.64.6.15) by DFLE101.ent.ti.com (10.64.6.22) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1261.35 via Frontend Transport; Wed, 18 Apr 2018 13:56:13 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by dflp32.itg.ti.com (8.14.3/8.13.8) with ESMTP id w3IIuD2d016602; Wed, 18 Apr 2018 13:56:13 -0500 Date: Wed, 18 Apr 2018 13:56:13 -0500 From: Bin Liu To: Johan Hovold CC: Greg Kroah-Hartman , Alan Stern , Arnd Bergmann , Kishon Vijay Abraham I , Martin Blumenstingl , , Subject: Re: [PATCH 0/3] USB: musb: dsps: phy fix and DT-topology support Message-ID: <20180418185613.GH14921@uda0271908> Mail-Followup-To: Bin Liu , Johan Hovold , Greg Kroah-Hartman , Alan Stern , Arnd Bergmann , Kishon Vijay Abraham I , Martin Blumenstingl , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org References: <20180413151505.32663-1-johan@kernel.org> <20180418162015.GG14921@uda0271908> <20180418184640.GJ9198@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20180418184640.GJ9198@localhost> User-Agent: Mutt/1.5.21 (2010-09-15) X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 18, 2018 at 08:46:40PM +0200, Johan Hovold wrote: > On Wed, Apr 18, 2018 at 11:20:15AM -0500, Bin Liu wrote: > > Johan, > > > > On Fri, Apr 13, 2018 at 05:15:02PM +0200, Johan Hovold wrote: > > > I've been carrying a patch out-of-tree since my work on improving the > > > USB device-tree support which is needed to be able to describe USB > > > topologies for musb based controllers. > > > > > > This patch, which associates the platform controller device with the > > > glue device device-tree node, did not play well with the recent changes > > > which added generic phy support to USB core however. > > > > > > Like the recent dwc2 regression fixed by Arnd after the device-tree > > > #phy-cell changes, the generic phy code in USB core can now also fail > > > indefinitly with -EPROBE_DEFER when the controller uses a legacy USB > > > phy. > > > > > > The second patch addresses this for musb, which handles its own (legacy > > > and generic) phys, but something more may possibly now be needed for > > > other platforms with legacy phys. > > > > > > In the process of debugging this, I stumbled over another issue which > > > caused the dsps legacy phy init two be called twice on every probe and > > > which is fixed by the first patch. > > > > > > Johan > > > > > > > > > Johan Hovold (3): > > > USB: musb: dsps: drop duplicate phy initialisation > > > USB: musb: host: prevent core phy initialisation > > > > Are the two bugs only affecting you with your out-of-tree patch? It > > seems don't have any functional impact for me. I need to make a decision > > if these two patches need to go to the stable trees... > > The first bug is independent of the third patch (the "out-of-tree" > patch), but as Uwe also noted it seems to be mostly benign since it took > two years for it to be discovered. For that reason, and to minimise the > risk of any stable regressions, I did not mark it for stable. > > The second fix is really only needed with the third of_node patch since > I don't think any of the glue drivers propagates the device-tree node in > this way currently. Hence it could also wait for 3.18, and it is in any > case not stable material as the generic-phy support in USB core is new > in 3.17. Great, thanks for confirming. I will not send them for stable trees. > > Note that other host controllers may have a device-tree node with > associated legacy-phys however and that this could now lead to similar > problems starting with 3.17. regards, -Bin.