linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] dts: arm64: add LS1046A DPAA QBMan nodes
Date: Fri, 31 Mar 2017 10:29:43 +0800	[thread overview]
Message-ID: <20170331022941.GJ683@dragon> (raw)
In-Reply-To: <1490884672-18294-4-git-send-email-madalin.bucur@nxp.com>

On Thu, Mar 30, 2017 at 05:37:52PM +0300, Madalin Bucur wrote:
> Add the QBMan device tree nodes for LS1046A devices.
> 
> Signed-off-by: Roy Pledge <roy.pledge@nxp.com>
> Signed-off-by: Madalin Bucur <madalin.bucur@nxp.com>
> ---
>  arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 52 ++++++++++++++++++++++++++
>  1 file changed, 52 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
> index 4a164b8..67e073a 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
> @@ -268,6 +268,30 @@
>  			};
>  		};
>  
> +		qman: qman at 1880000 {
> +			compatible = "fsl,qman";
> +			reg = <0x00 0x1880000 0x0 0x10000>;
> +			interrupts = <0 45 0x4>;
> +			memory-region = <&qman_fqd &qman_pfdr>;
> +
> +		};
> +
> +		bman: bman at 1890000 {
> +			compatible = "fsl,bman";
> +			reg = <0x00 0x1890000 0x0 0x10000>;
> +			interrupts = <0 45 0x4>;
> +			memory-region = <&bman_fbpr>;
> +
> +		};
> +
> +		qportals: qman-portals at 500000000 {
> +			ranges = <0x0 0x5 0x00000000 0x8000000>;
> +		};
> +
> +		bportals: bman-portals at 508000000 {
> +			ranges = <0x0 0x5 0x08000000 0x8000000>;
> +		};
> +
>  		dcfg: dcfg at 1ee0000 {
>  			compatible = "fsl,ls1046a-dcfg", "syscon";
>  			reg = <0x0 0x1ee0000 0x0 0x10000>;
> @@ -592,4 +616,32 @@
>  			clocks = <&clockgen 4 1>;
>  		};
>  	};
> +
> +	reserved-memory {
> +		#address-cells = <2>;
> +		#size-cells = <2>;
> +		ranges;
> +
> +		bman_fbpr: bman-fbpr {
> +			compatible = "shared-dma-pool";
> +			size = <0 0x1000000>;
> +			alignment = <0 0x1000000>;
> +			no-map;
> +		};

Please have a newline between nodes.

Shawn

> +		qman_fqd: qman-fqd {
> +			compatible = "shared-dma-pool";
> +			size = <0 0x800000>;
> +			alignment = <0 0x800000>;
> +			no-map;
> +		};
> +		qman_pfdr: qman-pfdr {
> +			compatible = "shared-dma-pool";
> +			size = <0 0x2000000>;
> +			alignment = <0 0x2000000>;
> +			no-map;
> +		};
> +	};
>  };
> +
> +#include "qoriq-qman1-portals.dtsi"
> +#include "qoriq-bman1-portals.dtsi"
> -- 
> 2.1.0
> 

  reply	other threads:[~2017-03-31  2:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 14:37 [PATCH 0/3] introduce QorIQ DPAA 1.x QBMan device tree nodes Madalin Bucur
2017-03-30 14:37 ` [PATCH 1/3] dts: arm64: add DPAA QBMan portals Madalin Bucur
2017-03-31  1:49   ` Shawn Guo
2017-05-12 14:14     ` Madalin-Cristian Bucur
2017-03-30 14:37 ` [PATCH 2/3] dts: arm64: add LS1043A DPAA QBMan nodes Madalin Bucur
2017-03-31  2:02   ` Shawn Guo
2017-05-12 14:14     ` Madalin-Cristian Bucur
2017-03-30 14:37 ` [PATCH 3/3] dts: arm64: add LS1046A " Madalin Bucur
2017-03-31  2:29   ` Shawn Guo [this message]
2017-05-12 14:14     ` Madalin-Cristian Bucur

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=20170331022941.GJ683@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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).