From: Shawn Guo <shawnguo@kernel.org>
To: Peng Ma <peng.ma@nxp.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
Wen He <wen.he_1@nxp.com>,
linux-kernel@vger.kernel.org, leoyang.li@nxp.com,
zw@zh-kernel.org, vkoul@kernel.org, robh+dt@kernel.org,
dmaengine@vger.kernel.org, dan.j.williams@intel.com,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [v11 6/7] arm64: dts: ls1046a: add qdma device tree nodes
Date: Thu, 6 Dec 2018 09:05:33 +0800 [thread overview]
Message-ID: <20181206010531.GR3987@dragon> (raw)
In-Reply-To: <20181030023604.34027-6-peng.ma@nxp.com>
On Tue, Oct 30, 2018 at 10:36:03AM +0800, Peng Ma wrote:
> add the qDMA device tree nodes for LS1046A devices.
>
> Signed-off-by: Wen He <wen.he_1@nxp.com>
> Signed-off-by: Peng Ma <peng.ma@nxp.com>
> ---
> change in v11:
> - no
>
> arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 21 +++++++++++++++++++++
> 1 files changed, 21 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
> index ef83786..dc65318 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
> @@ -704,6 +704,27 @@
> <0000 0 0 4 &gic GIC_SPI 154 IRQ_TYPE_LEVEL_HIGH>;
> };
>
> + qdma: dma-controller@8380000 {
> + compatible = "fsl,ls1046a-qdma", "fsl,ls1021a-qdma";
> + reg = <0x0 0x8380000 0x0 0x1000>, /* Controller regs */
> + <0x0 0x8390000 0x0 0x10000>, /* Status regs */
> + <0x0 0x83a0000 0x0 0x40000>; /* Block regs */
> + interrupts = <0 153 0x4>,
> + <0 39 0x4>,
> + <0 40 0x4>,
> + <0 41 0x4>,
> + <0 42 0x4>;
Use GIC_SPI and IRQ_TYPE_xxx defines.
Shawn
> + interrupt-names = "qdma-error", "qdma-queue0",
> + "qdma-queue1", "qdma-queue2", "qdma-queue3";
> + dma-channels = <8>;
> + block-number = <1>;
> + block-offset = <0x10000>;
> + fsl,dma-queues = <2>;
> + status-sizes = <64>;
> + queue-sizes = <64 64>;
> + big-endian;
> + };
> +
> };
>
> reserved-memory {
> --
> 1.7.1
>
next prev parent reply other threads:[~2018-12-06 1:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 2:35 [v11 1/7] dmaengine: fsldma: Replace DMA_IN/OUT by FSL_DMA_IN/OUT Peng Ma
2018-10-30 2:35 ` [v11 2/7] dmaengine: fsldma: Adding macro FSL_DMA_IN/OUT implement for ARM platform Peng Ma
2018-10-30 2:36 ` [v11 3/7] dmaengine: fsl-qdma: Add qDMA controller driver for Layerscape SoCs Peng Ma
2018-10-30 2:36 ` [v11 4/7] arm: dts: ls1021a: add qdma device tree nodes Peng Ma
2018-12-06 1:02 ` Shawn Guo
2018-10-30 2:36 ` [v11 5/7] arm64: dts: ls1043a: " Peng Ma
2018-12-06 1:04 ` Shawn Guo
2018-10-30 2:36 ` [v11 6/7] arm64: dts: ls1046a: " Peng Ma
2018-12-06 1:05 ` Shawn Guo [this message]
2018-12-06 11:04 ` Peng Ma
2018-10-30 2:36 ` [v11 7/7] dt-bindings: fsl-qdma: Add NXP Layerscpae qDMA controller bindings Peng Ma
2018-12-05 17:49 ` [v11 1/7] dmaengine: fsldma: Replace DMA_IN/OUT by FSL_DMA_IN/OUT Vinod Koul
2018-12-06 11:24 ` Peng Ma
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=20181206010531.GR3987@dragon \
--to=shawnguo@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=peng.ma@nxp.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=wen.he_1@nxp.com \
--cc=zw@zh-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).