From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: mv_xor_v2: new driver
Date: Sun, 21 Feb 2016 20:53:49 -0600 [thread overview]
Message-ID: <20160222025349.GC15973@rob-hp-laptop> (raw)
In-Reply-To: <1455523083-25506-1-git-send-email-thomas.petazzoni@free-electrons.com>
On Mon, Feb 15, 2016 at 08:58:03AM +0100, Thomas Petazzoni wrote:
> The new mv_xor_v2 driver supports the XOR engines found in the 64-bits
> ARM from Marvell of the Armada 7K and Armada 8K family. This XOR
> engine is a completely new hardware block, entirely different from the
> one used on previous Marvell Armada platforms, which use the existing
> mv_xor driver.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> .../devicetree/bindings/dma/mv-xor-v2.txt | 19 +
> drivers/dma/Kconfig | 13 +
> drivers/dma/Makefile | 1 +
> drivers/dma/mv_xor_v2.c | 880 +++++++++++++++++++++
> 4 files changed, 913 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/mv-xor-v2.txt
> create mode 100644 drivers/dma/mv_xor_v2.c
>
> diff --git a/Documentation/devicetree/bindings/dma/mv-xor-v2.txt b/Documentation/devicetree/bindings/dma/mv-xor-v2.txt
> new file mode 100644
> index 0000000..0a03dcf
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/mv-xor-v2.txt
> @@ -0,0 +1,19 @@
> +* Marvell XOR v2 engines
> +
> +Required properties:
> +- compatible: Should be "marvell,mv-xor-v2"
and an SoC specific compatible please.
"marvell,mv" is a bit redundant.
> +- reg: Should contain registers location and length (two sets)
> + the first set is the DMA registers
> + the second set is the global registers
> +- msi-parent: Phandle to the MSI-capable interrupt controller used for
> + interrupts.
> +
> +Example:
> +
> + xor0 at 400000 {
> + compatible = "marvell,mv-xor-v2";
> + reg = <0x400000 0x1000>,
> + <0x410000 0x1000>;
> + msi-parent = <&gic_v2m0>;
> + dma-coherent;
> + };
next prev parent reply other threads:[~2016-02-22 2:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 7:58 [PATCH] dma: mv_xor_v2: new driver Thomas Petazzoni
2016-02-15 9:09 ` kbuild test robot
2016-02-15 9:50 ` Thomas Petazzoni
2016-02-15 9:59 ` Marc Zyngier
2016-02-15 10:58 ` Thomas Petazzoni
2016-02-15 9:34 ` kbuild test robot
2016-02-15 9:34 ` [PATCH] dma: mv_xor_v2: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-02-15 9:56 ` [PATCH] dma: mv_xor_v2: new driver kbuild test robot
2016-02-22 2:53 ` Rob Herring [this message]
2016-02-22 7:21 ` Thomas Petazzoni
2016-02-22 20:02 ` Rob Herring
2016-02-22 3:27 ` Vinod Koul
2016-02-22 9:16 ` Thomas Petazzoni
2016-02-22 19:58 ` Rob Herring
2016-02-23 3:02 ` Vinod Koul
2016-06-15 14:08 ` Thomas Petazzoni
2016-06-15 16:41 ` Vinod Koul
2016-06-16 12:42 ` Thomas Petazzoni
2016-06-17 2:39 ` Vinod Koul
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=20160222025349.GC15973@rob-hp-laptop \
--to=robh@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