devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"maintainer:BROADCOM IPROC GBIT ETHERNET DRIVER"
	<bcm-kernel-feedback-list@broadcom.com>,
	"Doug Berger" <opendmb@gmail.com>, "Ray Jui" <rjui@broadcom.com>,
	"Scott Branden" <sbranden@broadcom.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"moderated list:BROADCOM IPROC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next 7/7] dt-bindings: net: Convert iProc MDIO mux to YAML
Date: Wed, 1 Dec 2021 13:06:58 -0600	[thread overview]
Message-ID: <YafH0nADqO7DTU4A@robh.at.kernel.org> (raw)
In-Reply-To: <20211201041228.32444-8-f.fainelli@gmail.com>

On Tue, Nov 30, 2021 at 08:12:28PM -0800, Florian Fainelli wrote:
> Conver the Broadcom iProc MDIO mux Device Tree binding to YAML.
> 
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
>  .../bindings/net/brcm,mdio-mux-iproc.txt      | 62 --------------
>  .../bindings/net/brcm,mdio-mux-iproc.yaml     | 80 +++++++++++++++++++
>  2 files changed, 80 insertions(+), 62 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.txt
>  create mode 100644 Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.yaml
> 
> diff --git a/Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.txt b/Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.txt
> deleted file mode 100644
> index deb9e852ea27..000000000000
> --- a/Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.txt
> +++ /dev/null
> @@ -1,62 +0,0 @@
> -Properties for an MDIO bus multiplexer found in Broadcom iProc based SoCs.
> -
> -This MDIO bus multiplexer defines buses that could be internal as well as
> -external to SoCs and could accept MDIO transaction compatible to C-22 or
> -C-45 Clause. When child bus is selected, one needs to select these two
> -properties as well to generate desired MDIO transaction on appropriate bus.
> -
> -Required properties in addition to the generic multiplexer properties:
> -
> -MDIO multiplexer node:
> -- compatible: brcm,mdio-mux-iproc.
> -
> -Every non-ethernet PHY requires a compatible so that it could be probed based
> -on this compatible string.
> -
> -Optional properties:
> -- clocks: phandle of the core clock which drives the mdio block.
> -
> -Additional information regarding generic multiplexer properties can be found
> -at- Documentation/devicetree/bindings/net/mdio-mux.yaml
> -
> -
> -for example:
> -		mdio_mux_iproc: mdio-mux@66020000 {
> -			compatible = "brcm,mdio-mux-iproc";
> -			reg = <0x66020000 0x250>;
> -			#address-cells = <1>;
> -			#size-cells = <0>;
> -
> -			mdio@0 {
> -				reg = <0x0>;
> -				#address-cells = <1>;
> -				#size-cells = <0>;
> -
> -				pci_phy0: pci-phy@0 {
> -					compatible = "brcm,ns2-pcie-phy";
> -					reg = <0x0>;
> -					#phy-cells = <0>;
> -				};
> -			};
> -
> -			mdio@7 {
> -				reg = <0x7>;
> -				#address-cells = <1>;
> -				#size-cells = <0>;
> -
> -				pci_phy1: pci-phy@0 {
> -					compatible = "brcm,ns2-pcie-phy";
> -					reg = <0x0>;
> -					#phy-cells = <0>;
> -				};
> -			};
> -			mdio@10 {
> -				reg = <0x10>;
> -				#address-cells = <1>;
> -				#size-cells = <0>;
> -
> -				gphy0: eth-phy@10 {
> -					reg = <0x10>;
> -				};
> -			};
> -		};
> diff --git a/Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.yaml b/Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.yaml
> new file mode 100644
> index 000000000000..a576fb87bfc8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.yaml
> @@ -0,0 +1,80 @@
> +# SPDX-License-Identifier: GPL-2.0

All Broadcom authors on the original. Please add BSD-2-Clause.

> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/brcm,mdio-mux-iproc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MDIO bus multiplexer found in Broadcom iProc based SoCs.
> +
> +maintainers:
> +  - Florian Fainelli <f.fainelli@gmail.com>
> +
> +description:
> +  This MDIO bus multiplexer defines buses that could be internal as well as
> +  external to SoCs and could accept MDIO transaction compatible to C-22 or
> +  C-45 Clause. When child bus is selected, one needs to select these two
> +  properties as well to generate desired MDIO transaction on appropriate bus.
> +
> +allOf:
> +  - $ref: /schemas/net/mdio-mux.yaml#
> +
> +properties:
> +  compatible:
> +    const: brcm,mdio-mux-iproc
> +
> +  reg:
> +    maxItems: 1
> +
> +  clocks:
> +    maxItems: 1
> +    description: core clock driving the MDIO block
> +
> +
> +required:
> +  - compatible
> +  - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    mdio_mux_iproc: mdio-mux@66020000 {
> +        compatible = "brcm,mdio-mux-iproc";
> +        reg = <0x66020000 0x250>;
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        mdio@0 {
> +           reg = <0x0>;
> +           #address-cells = <1>;
> +           #size-cells = <0>;
> +
> +           pci_phy0: pci-phy@0 {
> +              compatible = "brcm,ns2-pcie-phy";
> +              reg = <0x0>;
> +              #phy-cells = <0>;
> +           };
> +        };
> +
> +        mdio@7 {
> +           reg = <0x7>;
> +           #address-cells = <1>;
> +           #size-cells = <0>;
> +
> +           pci_phy1: pci-phy@0 {
> +              compatible = "brcm,ns2-pcie-phy";
> +              reg = <0x0>;
> +              #phy-cells = <0>;
> +           };
> +        };
> +
> +        mdio@10 {
> +           reg = <0x10>;
> +           #address-cells = <1>;
> +           #size-cells = <0>;
> +
> +           gphy0: eth-phy@10 {
> +              reg = <0x10>;
> +           };
> +        };
> +    };
> -- 
> 2.25.1
> 
> 

  parent reply	other threads:[~2021-12-01 19:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01  4:12 [PATCH net-next 0/7] Broadcom DT bindings conversion to YAML Florian Fainelli
2021-12-01  4:12 ` [PATCH net-next 1/7] dt-bindings: net: brcm,unimac-mdio: reg-names is optional Florian Fainelli
2021-12-01  4:12 ` [PATCH net-next 2/7] dt-bindings: net: brcm,unimac-mdio: Update maintainers for binding Florian Fainelli
2021-12-01  4:12 ` [PATCH net-next 3/7] dt-bindings: net: Document moca PHY interface Florian Fainelli
2021-12-01 14:33   ` Rob Herring
2021-12-01 17:15     ` Florian Fainelli
2021-12-01 18:28       ` Rob Herring
2021-12-01  4:12 ` [PATCH net-next 4/7] dt-bindings: net: Convert GENET binding to YAML Florian Fainelli
2021-12-01 14:33   ` Rob Herring
2021-12-01  4:12 ` [PATCH net-next 5/7] dt-bindings: net: Convert AMAC " Florian Fainelli
2021-12-01  4:12 ` [PATCH net-next 6/7] dt-bindings: net: Convert SYSTEMPORT " Florian Fainelli
2021-12-01 14:33   ` Rob Herring
2021-12-01  4:12 ` [PATCH net-next 7/7] dt-bindings: net: Convert iProc MDIO mux " Florian Fainelli
2021-12-01 14:33   ` Rob Herring
2021-12-01 19:06   ` Rob Herring [this message]
2021-12-01 19:48     ` Florian Fainelli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YafH0nADqO7DTU4A@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=opendmb@gmail.com \
    --cc=rafal@milecki.pl \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).