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=-2.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 29117C48BE0 for ; Fri, 11 Jun 2021 11:27:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0A58D613C8 for ; Fri, 11 Jun 2021 11:27:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231520AbhFKL3l (ORCPT ); Fri, 11 Jun 2021 07:29:41 -0400 Received: from mail-pj1-f54.google.com ([209.85.216.54]:38735 "EHLO mail-pj1-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230248AbhFKL3k (ORCPT ); Fri, 11 Jun 2021 07:29:40 -0400 Received: by mail-pj1-f54.google.com with SMTP id m13-20020a17090b068db02901656cc93a75so5672025pjz.3; Fri, 11 Jun 2021 04:27:42 -0700 (PDT) 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=h4XBx6hy/8HemTestI8gx5CVIEJQPh5SHNT2c3CXnb4=; b=rcciTaLnGKf0bY+pPO8FwxoOXt0lVZm79aIo1gkrehaurfpJDOI9ugW/6rpoprP2p0 eR/c/rDamGM2HF4c0TNczIAXWs7O9JyvxdCPnkBGndSC0i767zSjoV+BmvfHVBSqQWyV iFlBuXhampJ7t8Cb7+xV3/yCngTtHrPHnmeqY7OCasqUjntyocJljMWz1CTpzHNnTzpb LVx6xMLL1nB4S/kpUW/NJ9s6Zysk3DvGmYCA7bXvEqXmQqRkn6Lc9tnp3WIZbRd7vFRI oWbbq5BXntVc/zufWP6Lz0wJhvzSivys4gB6sPnbseSYghKvWidvHxifW9jRBajTumSr qn4A== 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=h4XBx6hy/8HemTestI8gx5CVIEJQPh5SHNT2c3CXnb4=; b=mFuJr2jNjg56fuqQouxJkqGDxTM8UNeTFMV5RkHgDr2A8CQPH90OaoBHTaxB91zPEu T+ZllQ1weay6zU7+toMBC+dvVNsf3Oz3BxBCSSw50W44yEmhEgZaU+A0CMkux79iB5Ow kuX38SlvRuqXUcgkzNlQw79873zKMnzN0zForW+K+0htd1GdF+e+nlbDqQQMbMR7njXL uGhZfzGO1Fb3o587YZINb9fhPtUUvb3FnC41jXUvKIbDfmoXVCBNfmE+8xr3U+Vj1DY/ ZOZ8kYo1lUwIZ9aiAExeZ1vGBrV5G4Ib//7PyvyCC7KmuCWGH/SNIYc3rnVXk48agNnE X7Ng== X-Gm-Message-State: AOAM532T/AcTkuLs1mjS9kAD6rZJxeHhzX5+c3taSKpGa2tDshiYw2cd aoC2gJoGu/iSbSt7W6liOTJz7ukC2JkS5mSXSOY= X-Google-Smtp-Source: ABdhPJzu9xzYtnBrRvh2AQos0EplFhBidiSQVytvzwTGQJ7UQDj+xrv8IWDD18RS/gAhTpmrdgRZsL5uHfb4I1HK1vU= X-Received: by 2002:a17:90a:80c5:: with SMTP id k5mr8780907pjw.129.1623410802452; Fri, 11 Jun 2021 04:26:42 -0700 (PDT) MIME-Version: 1.0 References: <20210611105401.270673-1-ciorneiioana@gmail.com> <20210611105401.270673-4-ciorneiioana@gmail.com> In-Reply-To: <20210611105401.270673-4-ciorneiioana@gmail.com> From: Andy Shevchenko Date: Fri, 11 Jun 2021 14:26:26 +0300 Message-ID: Subject: Re: [PATCH net-next v9 03/15] net: phy: Introduce phy related fwnode functions To: Ioana Ciornei Cc: "David S. Miller" , Jakub Kicinski , Heiner Kallweit , netdev , Grant Likely , "Rafael J . Wysocki" , Jeremy Linton , Andrew Lunn , Florian Fainelli , Russell King - ARM Linux admin , Heikki Krogerus , Marcin Wojtas , Pieter Jansen Van Vuuren , Jon , Saravana Kannan , Randy Dunlap , Calvin Johnson , Cristi Sovaiala , Florin Laurentiu Chiculita , Madalin Bucur , linux-arm Mailing List , Diana Madalina Craciun , ACPI Devel Maling List , Linux Kernel Mailing List , "linux.cj" , Laurentiu Tudor , Len Brown , "Rafael J . Wysocki" , Ioana Ciornei Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Fri, Jun 11, 2021 at 1:54 PM Ioana Ciornei wrote: > > From: Calvin Johnson > > Define fwnode_phy_find_device() to iterate an mdiobus and find the > phy device of the provided phy fwnode. Additionally define > device_phy_find_device() to find phy device of provided device. > > Define fwnode_get_phy_node() to get phy_node using named reference. using a named ... > +struct fwnode_handle *fwnode_get_phy_node(struct fwnode_handle *fwnode) > +{ > + struct fwnode_handle *phy_node; > + > + /* Only phy-handle is used for ACPI */ > + phy_node = fwnode_find_reference(fwnode, "phy-handle", 0); > + if (is_acpi_node(fwnode) || !IS_ERR(phy_node)) > + return phy_node; > + phy_node = fwnode_find_reference(fwnode, "phy", 0); > + if (IS_ERR(phy_node)) > + phy_node = fwnode_find_reference(fwnode, "phy-device", 0); > + return phy_node; Looking into the patterns in this code I would perhaps refactor it the following way: /* First try "phy-handle" as most common in use */ phy_node = fwnode_find_reference(fwnode, "phy-handle", 0); /* Only phy-handle is used for ACPI */ if (is_acpi_node(fwnode)) return phy_node; if (!IS_ERR(phy_node)) return phy_node; /* Try "phy" reference */ phy_node = fwnode_find_reference(fwnode, "phy", 0); if (!IS_ERR(phy_node)) return phy_node; /* At last try "phy-device" reference */ return fwnode_find_reference(fwnode, "phy-device", 0); > +} -- With Best Regards, Andy Shevchenko