From: Scott Wood <scottwood@freescale.com>
To: <hongbo.zhang@freescale.com>
Cc: devicetree@vger.kernel.org, vinod.koul@intel.com,
linux-kernel@vger.kernel.org,
Hongbo Zhang <hongbo.zhang@freescale.com>,
djbw@fb.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5 2/4] DMA: Freescale: Add new 8-channel DMA engine device tree nodes
Date: Wed, 24 Jul 2013 14:29:08 -0500 [thread overview]
Message-ID: <1374694148.15592.61@snotra> (raw)
In-Reply-To: <1374646870-5162-3-git-send-email-hongbo.zhang@freescale.com> (from hongbo.zhang@freescale.com on Wed Jul 24 01:21:07 2013)
On 07/24/2013 01:21:07 AM, hongbo.zhang@freescale.com wrote:
> From: Hongbo Zhang <hongbo.zhang@freescale.com>
>=20
> Freescale QorIQ T4 and B4 introduce new 8-channel DMA engines, this =20
> patch add
> the device tree nodes for them.
>=20
> Signed-off-by: Hongbo Zhang <hongbo.zhang@freescale.com>
> ---
> .../devicetree/bindings/powerpc/fsl/dma.txt | 66 =20
> ++++++++++++++++
> arch/powerpc/boot/dts/fsl/b4si-post.dtsi | 4 +-
> arch/powerpc/boot/dts/fsl/elo3-dma-0.dtsi | 81 =20
> ++++++++++++++++++++
> arch/powerpc/boot/dts/fsl/elo3-dma-1.dtsi | 81 =20
> ++++++++++++++++++++
> arch/powerpc/boot/dts/fsl/t4240si-post.dtsi | 4 +-
> 5 files changed, 232 insertions(+), 4 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
>=20
> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt =20
> b/Documentation/devicetree/bindings/powerpc/fsl/dma.txt
> index ed703d9..54a023b2 100644
> --- a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt
> +++ b/Documentation/devicetree/bindings/powerpc/fsl/dma.txt
> @@ -130,6 +130,72 @@ Example:
> };
> };
>=20
> +** Freescale Elo3 DMA Controller
> + This is EloPlus controller with 8 channels, used in Freescale =20
> Txxx and Bxxx
> + series chips, such as t1040, t4240, b4860.
> +
> +Required properties:
> +
> +- compatible : should be "fsl,elo3-dma"
Should include "fsl,elo3-dma". There's nothing different about elo3 =20
versus elo/eloplus regarding whether fsl,CHIP-dma is allowed. I'd just =20
drop the references to fsl,CHIP-dma throughout the binding, and phrase =20
the compatible description as "must include" rather than "must be" so =20
that additional strings are allowed.
-Scott=
next prev parent reply other threads:[~2013-07-24 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 6:21 [PATCH v5 0/4] DMA: Freescale: Add support for 8-channel DMA engine hongbo.zhang
2013-07-24 6:21 ` [PATCH v5 1/4] DMA: Freescale: revise device tree binding document hongbo.zhang
2013-07-24 6:21 ` [PATCH v5 2/4] DMA: Freescale: Add new 8-channel DMA engine device tree nodes hongbo.zhang
2013-07-24 19:29 ` Scott Wood [this message]
2013-07-24 6:21 ` [PATCH v5 3/4] DMA: Freescale: update driver to support 8-channel DMA engine hongbo.zhang
2013-07-24 19:30 ` Scott Wood
2013-07-24 6:21 ` [PATCH v5 4/4] DMA: Freescale: eliminate a compiling warning hongbo.zhang
2013-07-24 19:33 ` Scott Wood
2013-07-25 2:46 ` Hongbo Zhang
2013-07-24 6:34 ` [PATCH v5 0/4] DMA: Freescale: Add support for 8-channel DMA engine Li Yang
2013-07-24 6:47 ` Li Yang
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=1374694148.15592.61@snotra \
--to=scottwood@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=djbw@fb.com \
--cc=hongbo.zhang@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).