devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: alex.williams@ettus.com
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, davem@davemloft.net,
	mark.rutland@arm.com, mdf@kernel.org, keescook@chromium.org,
	Alex Williams <alex.williams@ni.com>
Subject: Re: [PATCH net-next 2/2] net: nixge: Update device-tree bindings with v3.00
Date: Mon, 12 Nov 2018 10:24:30 -0600	[thread overview]
Message-ID: <5bea0e95.1c69fb81.88799.a282@mx.google.com> (raw)
In-Reply-To: <20181029231447.3690-2-alex.williams@ettus.com>

On Mon, Oct 29, 2018 at 04:14:47PM -0700, alex.williams@ettus.com wrote:
> From: Alex Williams <alex.williams@ni.com>
> 
> Now the DMA engine is free to float elsewhere in the system map.
> 
> Signed-off-by: Alex Williams <alex.williams@ni.com>
> ---
>  Documentation/devicetree/bindings/net/nixge.txt | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/net/nixge.txt b/Documentation/devicetree/bindings/net/nixge.txt
> index e55af7f0881a..d0f9fb520578 100644
> --- a/Documentation/devicetree/bindings/net/nixge.txt
> +++ b/Documentation/devicetree/bindings/net/nixge.txt
> @@ -1,8 +1,14 @@
>  * NI XGE Ethernet controller
>  
>  Required properties:
> -- compatible: Should be "ni,xge-enet-2.00"
> -- reg: Address and length of the register set for the device
> +- compatible: Should be "ni,xge-enet-3.00", but can be "ni,xge-enet-2.00" for
> +              older device trees with DMA engines co-located in the address map,
> +              with the one reg entry to describe the whole device.
> +- reg: Address and length of the register set for the device. It contains the
> +       information of registers in the same order as described by reg-names.
> +- reg-names: Should contain the reg names
> +	"dma":  DMA engine control and status region
> +        "ctrl": MDIO and PHY control and status region
>  - interrupts: Should contain tx and rx interrupt
>  - interrupt-names: Should be "rx" and "tx"
>  - phy-mode: See ethernet.txt file in the same directory.
> @@ -13,7 +19,9 @@ Required properties:
>  Examples (10G generic PHY):
>  	nixge0: ethernet@40000000 {
>  		compatible = "ni,xge-enet-2.00";

Shouldn't the compatible change here?

> -		reg = <0x40000000 0x6000>;
> +		reg = <0x40000000 0x4000
> +		       0x41002000 0x2000>;
> +		reg-names = "dma", "ctrl";
>  
>  		nvmem-cells = <&eth1_addr>;
>  		nvmem-cell-names = "address";
> -- 
> 2.14.5
> 

  reply	other threads:[~2018-11-12 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 23:14 [PATCH net-next 1/2] net: nixge: Separate ctrl and dma resources alex.williams
2018-10-29 23:14 ` [PATCH net-next 2/2] net: nixge: Update device-tree bindings with v3.00 alex.williams
2018-11-12 16:24   ` Rob Herring [this message]
2018-11-12 23:41     ` Alex Williams
2018-11-13  0:26       ` Rob Herring
2018-10-29 23:37 ` [PATCH net-next 1/2] net: nixge: Separate ctrl and dma resources David Miller

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=5bea0e95.1c69fb81.88799.a282@mx.google.com \
    --to=robh@kernel.org \
    --cc=alex.williams@ettus.com \
    --cc=alex.williams@ni.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mdf@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).