devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Arun Parameswaran <arunp@broadcom.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH 1/4] dt-bindings: net: Broadcom iProc MDIO bus driver device tree binding
Date: Wed, 30 Sep 2015 14:36:02 -0700	[thread overview]
Message-ID: <560C55C2.3010906@gmail.com> (raw)
In-Reply-To: <1443645163-2822-2-git-send-email-arunp@broadcom.com>

On 30/09/15 13:32, Arun Parameswaran wrote:
> Add device tree binding documentation for the Broadcom iProc MDIO
> bus driver.
> 
> Signed-off-by: Arun Parameswaran <arunp@broadcom.com>
> ---
>  .../devicetree/bindings/net/brcm,iproc-mdio.txt    | 23 ++++++++++++++++++++++
>  1 file changed, 23 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/net/brcm,iproc-mdio.txt
> 
> diff --git a/Documentation/devicetree/bindings/net/brcm,iproc-mdio.txt b/Documentation/devicetree/bindings/net/brcm,iproc-mdio.txt
> new file mode 100644
> index 0000000..689f97c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/brcm,iproc-mdio.txt
> @@ -0,0 +1,23 @@
> +* Broadcom iProc MDIO bus controller
> +
> +Required properties:
> +- compatible: should be "brcm,iproc-mdio"
> +- reg: address and length of the register set for the MDIO interface
> +- #size-cells: must be 1
> +- #address-cells: must be 0
> +
> +Child nodes of this MDIO bus controller node are standard Ethernet PHY device
> +nodes as described in Documentation/devicetree/bindings/net/phy.txt
> +
> +Example:
> +
> +mdio@0x18002000 {

Sorry for not catching this earlier, you might want to drop the leading
0x here from your example, other than that:

Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
-- 
Florian

  reply	other threads:[~2015-09-30 21:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 20:32 [PATCH 0/4] Add support for Broadcom's iProc MDIO and Cygnus Ethernet PHY Arun Parameswaran
     [not found] ` <1443645163-2822-1-git-send-email-arunp-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-09-30 20:32   ` [PATCH 1/4] dt-bindings: net: Broadcom iProc MDIO bus driver device tree binding Arun Parameswaran
2015-09-30 21:36     ` Florian Fainelli [this message]
     [not found]       ` <560C55C2.3010906-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-30 21:45         ` Arun Parameswaran
2015-09-30 20:32 ` [PATCH 2/4] net: phy: Broadcom iProc MDIO bus driver Arun Parameswaran
2015-09-30 21:36   ` Florian Fainelli
2015-09-30 20:32 ` [PATCH 3/4] net: phy: Add Broadcom phy library for common interfaces Arun Parameswaran
2015-09-30 21:13   ` kbuild test robot
2015-09-30 21:35   ` Florian Fainelli
2015-09-30 20:32 ` [PATCH 4/4] net: phy: Broadcom Cygnus internal Etherent PHY driver Arun Parameswaran
     [not found]   ` <1443645163-2822-5-git-send-email-arunp-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-09-30 21:37     ` Florian Fainelli
2015-09-30 21:43       ` Arun Parameswaran
2015-10-01  0:37   ` kbuild test robot

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=560C55C2.3010906@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=arunp@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).