From: Scott Wood <scottwood@freescale.com>
Cc: vinod.koul@intel.com, djbw@fb.com, leoli@freescale.com,
linuxppc-dev@lists.ozlabs.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, vakul@freescale.com,
Hongbo Zhang <hongbo.zhang@freescale.com>
Subject: Re: [PATCH v3 1/2] DMA: Freescale: Add new 8-channel DMA engine device tree nodes
Date: Mon, 15 Jul 2013 12:57:05 -0500 [thread overview]
Message-ID: <1373911025.8183.308@snotra> (raw)
In-Reply-To: <1373884499-24079-2-git-send-email-hongbo.zhang@freescale.com> (from hongbo.zhang@freescale.com on Mon Jul 15 05:34:58 2013)
On 07/15/2013 05:34:58 AM, hongbo.zhang@freescale.com wrote:
> From: Hongbo Zhang <hongbo.zhang@freescale.com>
>
> Freescale QorIQ T4 and B4 introduce new 8-channel DMA engines, this
> patch add
> the device tree nodes for them.
>
> Signed-off-by: Hongbo Zhang <hongbo.zhang@freescale.com>
> ---
> .../devicetree/bindings/powerpc/fsl/dma.txt | 8 +-
> arch/powerpc/boot/dts/fsl/elo3-dma-0.dtsi | 90
> ++++++++++++++++++++
> arch/powerpc/boot/dts/fsl/elo3-dma-1.dtsi | 90
> ++++++++++++++++++++
> arch/powerpc/boot/dts/fsl/t4240si-post.dtsi | 4 +-
> 4 files changed, 187 insertions(+), 5 deletions(-)
> create mode 100644 arch/powerpc/boot/dts/fsl/elo3-dma-0.dtsi
> create mode 100644 arch/powerpc/boot/dts/fsl/elo3-dma-1.dtsi
>
> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt
> b/Documentation/devicetree/bindings/powerpc/fsl/dma.txt
> index 2a4b4bc..8ee5732 100644
> --- a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt
> +++ b/Documentation/devicetree/bindings/powerpc/fsl/dma.txt
> @@ -76,10 +76,10 @@ Freescale PowerPC 85xx/86xx have on chip general
> purpose DMA controllers.
>
> Required properties:
>
> -- compatible : compatible list, contains 2 entries, first is
> +- compatible : compatible list, contains 3 entries, first is
> "fsl,CHIP-dma", where CHIP is the processor
> (mpc8540, mpc8540, etc.) and the second is
> - "fsl,eloplus-dma"
> + "fsl,eloplus-dma", the third is "fsl,elo3-dma"
The new device tree nodes have only one compatible in the list, not
three. And if you were to both fsl,eloplus-dma and fsl,elo3-dma on the
same node, fsl,elo3-dma should come first.
> - reg : <registers mapping for DMA general status reg>
> - cell-index : controller index. 0 for controller @ 0x21000,
> 1 for controller @ 0xc000
> @@ -100,7 +100,7 @@ Example:
> dma@21300 {
> #address-cells = <1>;
> #size-cells = <1>;
> - compatible = "fsl,mpc8540-dma", "fsl,eloplus-dma";
> + compatible = "fsl,mpc8540-dma", "fsl,eloplus-dma",
> "fsl,elo3-dma";
In addition to the above issue about ordering, mpc8540 does not have
elo3.
-Scott
next prev parent reply other threads:[~2013-07-15 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 10:34 [PATCH v3 0/2] DMA: Freescale: Add support for 8-channel DMA engine hongbo.zhang
2013-07-15 10:34 ` [PATCH v3 1/2] DMA: Freescale: Add new 8-channel DMA engine device tree nodes hongbo.zhang
2013-07-15 17:57 ` Scott Wood [this message]
2013-07-15 10:34 ` [PATCH v3 2/2] DMA: Freescale: update driver to support 8-channel DMA engine hongbo.zhang
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=1373911025.8183.308@snotra \
--to=scottwood@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=djbw@fb.com \
--cc=hongbo.zhang@freescale.com \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vakul@freescale.com \
--cc=vinod.koul@intel.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).