Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp2077461ybv; Fri, 14 Feb 2020 11:02:07 -0800 (PST) X-Google-Smtp-Source: APXvYqyNk+HeXPYbINKPhLJibCIpxW4cJhKOcFUf3X4NIEukWXgdGgS3IREpOBSA3d8A62pJor1X X-Received: by 2002:aca:5083:: with SMTP id e125mr2915376oib.96.1581706927061; Fri, 14 Feb 2020 11:02:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581706927; cv=none; d=google.com; s=arc-20160816; b=eRyGwOhWyHEPnZeG2LU0SXUdemMeyIDfvpzvO1VrIz5Nz8FNEztnyI2Td81XAtn++E 3ZwoyG46q9k1rjUma2Z/NG7I3m/VduyFgNzfIr/BK5PaMFp1bdPU9p3xZmQKMNrrpaNx BHA3wMiXxb6fMmstA8bt/LGzUX0fh808qOc5X5WU3Ob5ti8TiNc0jqoLa0vlR7ZomBBg Om4aRG4Jqps8DjJZL6o4e5xxn3djR6Ts72KBwSNNop7UO6dSP+HQLbMi2pXrqrV/MZHw 9Mn5sToe2QZlLgvKmvBRKawgcbNPQ1MhxsGDAL7GNyRuWbflw2U3RThm+rWgxrTd23lX R5ig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=lcAo2cRFw8x17fP3aIkMxC2GnRGns7uCksHDMjRNXaw=; b=OwPrf+YmlQHXqstjfVjLiToya/cFyDl9zAXI/hhJ7srpDgc0yBDKsHX++KOgrUIGev dZQaIwe5SC2ZFIsdVziztqTpy1cqARSs6X5vctcUD0yvYfvP20HEvG5UXldpxqrvFHhK wYfA9yfLsUimVraN+d5DjJe8eh8MlHrTy7rPyAst/jhKd7v7gWMO5/q2FdAc2hscD38C XwISercVFQvXnie/PW1cZa6mwIena6nQHxqXSKdrndhzDR3u8gq2ltemPJiRXU2/qVre ZskpYGToF22L9/3U8l5Am6pj0LW7RoWN8SWqlN3nedgb9tveBdF803MuWJQlf64xhQ3L hzVA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=RrbDf18P; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t184si3256178oig.184.2020.02.14.11.01.54; Fri, 14 Feb 2020 11:02:07 -0800 (PST) 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=@gmail.com header.s=20161025 header.b=RrbDf18P; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390247AbgBNSqJ (ORCPT + 99 others); Fri, 14 Feb 2020 13:46:09 -0500 Received: from mail-pf1-f196.google.com ([209.85.210.196]:36840 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389723AbgBNSqI (ORCPT ); Fri, 14 Feb 2020 13:46:08 -0500 Received: by mail-pf1-f196.google.com with SMTP id 185so5299907pfv.3; Fri, 14 Feb 2020 10:46:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lcAo2cRFw8x17fP3aIkMxC2GnRGns7uCksHDMjRNXaw=; b=RrbDf18PWY+2fPPPQRCgyupMcufV7Ny4wcwsGdOEEtsxZ8n4SIz0nQ15AsuI8LKx6z MJ8q3fbC03jYi1t/U7E53gh122fpTd8gehcq8oh4HGQdd54PshFBi2u0WhbgBUIXvfXF BNPispvDrlbRxPl/8EcYvO0C3qEowmJZ8uHiVjoxssrmVmcy9xN8o+gS6FFhK2Wmjz+8 +2+b5ZlZoiwfVjpEprNai/LE5rtCB2hXQYMJPKTtA3OtrQswlomQ+NLhGHRKz9mGP34q iurjMAKWExIUYE2f3A6NL19yI+YOHOoJsl3W+5MRRpgTqUNA9etGO5eriI4pdaLIVx3L ndCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lcAo2cRFw8x17fP3aIkMxC2GnRGns7uCksHDMjRNXaw=; b=ceIfjNpz9JtKKWCuWcZM+qfk4hQPjCYcOSAi3INokVLgdHU/LujHIECxQ9WftvTYwx lnS69w8WdstQkN1Ai31xa/WaLylPIll5Q3evhPpX8JOufBwUuAydhn973rSvirtFJixy uTj1s63xk37C2JS9ZEJg276a7teEqeeKUcOiXEZFhk9IDoggAaKdJnDrZX0RRAhVVFLP 3+dZylmUy678IwK7q1uJRDRYnM35tyaK/d7rmVqRMutXSsllxWTNFOV7Mkn2oz+eUAst cbf9IjXViNi+r1W6ZIRXMfc5bTg3BAk4chZHqBEEKQp9D8pc3QMP+RKDF1nwnCy3X8qn u/1A== X-Gm-Message-State: APjAAAU3zRXmDS5STERyiaBvSbGKaj/L2GjvZ/bQQPCPH97yLC6bX/he CUUI475LdAHfj5Nretzopda4II0CzKqW6sIGzssAfq5a/ds= X-Received: by 2002:a62:1a09:: with SMTP id a9mr4854899pfa.64.1581705968117; Fri, 14 Feb 2020 10:46:08 -0800 (PST) MIME-Version: 1.0 References: <20191104143713.11137-1-alexandre.torgue@st.com> <20200206133918.15012-1-youling257@gmail.com> <0c4a37a9-0a2e-e698-f423-53060854ea05@ti.com> <8bd72269-16ae-b24a-7144-44d22d668dc6@ti.com> <1cd5885d-7db4-59b9-ef2d-e3556f60ca68@st.com> In-Reply-To: <1cd5885d-7db4-59b9-ef2d-e3556f60ca68@st.com> From: Andy Shevchenko Date: Fri, 14 Feb 2020 20:46:00 +0200 Message-ID: Subject: Re: [PATCH] phy: core: Add consumer device link support To: Alexandre Torgue Cc: Kishon Vijay Abraham I , youling 257 , Yoshihiro Shimoda , Greg Kroah-Hartman , Linux Kernel Mailing List , USB , saravanak@google.com 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 On Mon, Feb 10, 2020 at 1:32 PM Alexandre Torgue wrote: > On 2/10/20 9:08 AM, Kishon Vijay Abraham I wrote: > > On 07/02/20 12:27 PM, youling 257 wrote: > >> test this diff, dwc3 work for my device, thanks. > >> > >> 2020-02-07 13:16 GMT+08:00, Kishon Vijay Abraham I : > >>> On 06/02/20 7:09 PM, youling257 wrote: > >>>> This patch cause "dwc3 dwc3.3.auto: failed to create device link to > >>>> dwc3.3.auto.ulpi" problem. > >>>> https://bugzilla.kernel.org/show_bug.cgi?id=206435 +1 to the report. Please revert for v5.6 or provide a fix ASAP! > >>> > >>> I'm suspecting there is some sort of reverse dependency with dwc3 ULPI. > >>> Can you try the following diff? > >>> > >>> diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c > >>> index 2eb28cc2d2dc..397311dcb116 100644 > >>> --- a/drivers/phy/phy-core.c > >>> +++ b/drivers/phy/phy-core.c > >>> @@ -687,7 +687,7 @@ struct phy *phy_get(struct device *dev, const char > >>> *string) > >>> > >>> get_device(&phy->dev); > >>> > >>> - link = device_link_add(dev, &phy->dev, DL_FLAG_STATELESS); > >>> + link = device_link_add(dev, &phy->dev, DL_FLAG_SYNC_STATE_ONLY); > >>> if (!link) { > >>> dev_err(dev, "failed to create device link to %s\n", > >>> dev_name(phy->dev.parent)); > >>> @@ -802,7 +802,7 @@ struct phy *devm_of_phy_get(struct device *dev, > >>> struct device_node *np, > >>> return phy; > >>> } > >>> > >>> - link = device_link_add(dev, &phy->dev, DL_FLAG_STATELESS); > >>> + link = device_link_add(dev, &phy->dev, DL_FLAG_SYNC_STATE_ONLY); > >>> if (!link) { > >>> dev_err(dev, "failed to create device link to %s\n", > >>> dev_name(phy->dev.parent)); > >>> @@ -851,7 +851,7 @@ struct phy *devm_of_phy_get_by_index(struct device > >>> *dev, struct device_node *np, > >>> *ptr = phy; > >>> devres_add(dev, ptr); > >>> > >>> - link = device_link_add(dev, &phy->dev, DL_FLAG_STATELESS); > >>> + link = device_link_add(dev, &phy->dev, DL_FLAG_SYNC_STATE_ONLY); > >>> if (!link) { > >>> dev_err(dev, "failed to create device link to %s\n", > >>> dev_name(phy->dev.parent));Parent > > > > Can you check if this doesn't affect the suspend/resume ordering? > > With this fix, suspend/resume ordering is broken on my side. What do you > think to keep the STATELESS flag and to only display a warn if > "device_link_add" returns an error ? It's not "smart" but it could > solved our issue. > > As a lot of improvements have been recently done on device link topic by > Saravana, we could check with him what is the way to follow. > > Regards > Alex > > > > > Thanks > > Kishon > > -- With Best Regards, Andy Shevchenko