From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <netdev-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id C183FC433FE
	for <netdev@archiver.kernel.org>; Fri, 25 Mar 2022 19:42:15 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S230508AbiCYTnr (ORCPT <rfc822;netdev@archiver.kernel.org>);
        Fri, 25 Mar 2022 15:43:47 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42512 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S231640AbiCYTnL (ORCPT
        <rfc822;netdev@vger.kernel.org>); Fri, 25 Mar 2022 15:43:11 -0400
Received: from vps0.lunn.ch (vps0.lunn.ch [185.16.172.187])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 508F2204AB6;
        Fri, 25 Mar 2022 12:17:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch;
        s=20171124; h=In-Reply-To:Content-Transfer-Encoding:Content-Disposition:
        Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:From:
        Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type:
        Content-Transfer-Encoding:Content-ID:Content-Description:Content-Disposition:
        In-Reply-To:References; bh=6slMIQlhEqm87aKxVQg6SnauUicp81NuO6xcMEdN73M=; b=BP
        SO9Ml0OnSkpW7WifUh6kWImgj8T0kfL25nez69TyGP1u6AZ+EAy6L9s0T3rV+1/8WTNkvKECPLwKk
        IK4c6S6fuKHNY1mGqxZH+GTViqoEKp98xLkHZauahf6tvvKvNL2Yb6K75ZrvMZWXtsfNs8WzfBjsS
        GdpZlNEQCGuAJ9c=;
Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2)
        (envelope-from <andrew@lunn.ch>)
        id 1nXopM-00Cg15-MW; Fri, 25 Mar 2022 19:38:24 +0100
Date:   Fri, 25 Mar 2022 19:38:24 +0100
From:   Andrew Lunn <andrew@lunn.ch>
To:     =?iso-8859-1?Q?Cl=E9ment_L=E9ger?= <clement.leger@bootlin.com>
Cc:     Heiner Kallweit <hkallweit1@gmail.com>,
        Russell King <linux@armlinux.org.uk>,
        "David S . Miller" <davem@davemloft.net>,
        Jakub Kicinski <kuba@kernel.org>,
        Paolo Abeni <pabeni@redhat.com>,
        Horatiu Vultur <horatiu.vultur@microchip.com>,
        Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
        Alexandre Belloni <alexandre.belloni@bootlin.com>,
        Allan Nielsen <allan.nielsen@microchip.com>,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next 1/5] net: mdio: fwnode: add fwnode_mdiobus_register()
Message-ID: <Yj4MIIu7Qtvv25Fs@lunn.ch>
References: <20220325172234.1259667-1-clement.leger@bootlin.com>
 <20220325172234.1259667-2-clement.leger@bootlin.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20220325172234.1259667-2-clement.leger@bootlin.com>
Precedence: bulk
List-ID: <netdev.vger.kernel.org>
X-Mailing-List: netdev@vger.kernel.org

On Fri, Mar 25, 2022 at 06:22:30PM +0100, Clément Léger wrote:
> In order to support software node description transparently, add fwnode
> support with fwnode_mdiobus_register(). This function behaves exactly
> like of_mdiobus_register() function but using the fwnode node agnostic
> API. This support might also be used to merge ACPI mdiobus support
> which is quite similar to the fwnode one.
> 
> Some part such as the whitelist matching are kept exclusively for OF
> nodes since it uses an of_device_id struct and seems tightly coupled
> with OF. Other parts are generic and will allow to move the existing
> OF support on top of this fwnode version.

Does fwnode have any documentation? How does a developer know what
properties can be passed? Should you be adding a

Documentation/fwnode/bindings/net/mdio.yaml ?

	Andrew