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=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=no 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 C597DC432BE for ; Fri, 27 Aug 2021 21:33:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9D1E960F91 for ; Fri, 27 Aug 2021 21:33:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231926AbhH0Ve3 (ORCPT ); Fri, 27 Aug 2021 17:34:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33846 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231696AbhH0Ve2 (ORCPT ); Fri, 27 Aug 2021 17:34:28 -0400 Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 65C3CC0613D9 for ; Fri, 27 Aug 2021 14:33:39 -0700 (PDT) Received: by mail-yb1-xb2f.google.com with SMTP id x140so15169920ybe.0 for ; Fri, 27 Aug 2021 14:33:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RZNyHeDVs2mzNxDgTuglWtbJQudBi+AgMRN4SZ0C/nY=; b=jVqEIc455Wtcw8ODTyXfnO/FQsEQDMK/It9z9OeJqHqx8p3YH0rnsTE3JppBBQ71ic hFAjlj8BEwrMpHu5dY26GEJrq9XNElRyt2SaSTsQQPeNiGInacBfUIwM47yAwiv52Cx6 cb5GcXIKp71l+SHcuTn0XmplTlgeszW/UdUC5gCMt1xJKxkcd9fGDlAao5HTZ6N1Xrka x1jACeUhmZYPrTZV4Sdl2PwtBWU2wCwz958GvC5DQjFa8/08MAVUxdRtI1csFaIvGlK+ lC13HteG3Oka7xoTpaaAHoKgIUm8l7vHSWN0P6G5nVDvLsPsESrPFwGNXA+XnpKiANxH gLzQ== 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=RZNyHeDVs2mzNxDgTuglWtbJQudBi+AgMRN4SZ0C/nY=; b=gra59yDsgDalBk5+1MgjQQT8rlayfyBR+rgZusgvJUTlPP1WrOsFj4WhGjdZr+9aW2 9Okh+iPG5inKPTF6h9zBll8wXA3OzW8aMmFNAqMQNTxTx3f5UtaJ2vjvFad1BzazSBsg KQmd9IkD4ZZe6yGok9KtoA9bboGhwaRv2QKXLHxZqUIao+g26WsMjgfFNqryaT74itu+ s5JVpnqxhzqfez/rZQrPjayA/gcmbZE31HA469J0JjhBlSuThMLBL8p5IqCX0NSP3yUS 682WhxtuCc0fJsoUU5YVTt8Q11UYDrf7fCu4b8rMWSi1uzSGfvoEQADdtnS+ZpUuWdyS Q/mQ== X-Gm-Message-State: AOAM532Yn+XHTjGEmOK9mOtVsAClXaIk8SqWvLOltYcLv8ZgB28AnZRj 1WjHi9haHCgpw6JlIE1Je9+YwXgP5aTnRXzShVDNaA== X-Google-Smtp-Source: ABdhPJz5+dNvgc2ixHXOwcDeo8jDfMW8Ql6QvMwMVQ6iLfDyfXrrjgP9Mg+KHQk+aYDhygWXhbGhxIhyAShRq9e5qmw= X-Received: by 2002:a25:d2c8:: with SMTP id j191mr8213434ybg.412.1630100018502; Fri, 27 Aug 2021 14:33:38 -0700 (PDT) MIME-Version: 1.0 References: <20210826074526.825517-1-saravanak@google.com> <20210826074526.825517-2-saravanak@google.com> In-Reply-To: From: Saravana Kannan Date: Fri, 27 Aug 2021 14:33:02 -0700 Message-ID: Subject: Re: [PATCH v1 1/2] driver core: fw_devlink: Add support for FWNODE_FLAG_BROKEN_PARENT To: Andrew Lunn Cc: Greg Kroah-Hartman , "Rafael J. Wysocki" , Linus Walleij , Vivien Didelot , Florian Fainelli , Vladimir Oltean , "David S. Miller" , Jakub Kicinski , Len Brown , Alvin Sipraga , kernel-team@android.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-acpi@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Fri, Aug 27, 2021 at 1:11 PM Andrew Lunn wrote: > > > > I've not yet looked at plain Ethernet drivers. This pattern could also > > > exist there. And i wonder about other complex structures, i2c bus > > > multiplexors, you can have interrupt controllers as i2c devices, > > > etc. So the general case could exist in other places. > > > > I haven't seen any generic issues like this reported so far. It's only > > after adding phy-handle that we are hitting these issues with DSA > > switches. > > Can you run your parser over the 2250 DTB blobs and see how many > children have dependencies on a parent? That could give us an idea how > many moles need whacking. And maybe, where in the tree they are > hiding? You are only responding to part of my email. As I said in my previous email: "There are plenty of cases where it's better to delay the child device's probe until the parent finishes. You even gave an example[7] where it would help avoid unnecessary deferred probes." Can you please give your thoughts on the rest of the points I made too? -Saravana