From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] Add XOR engine support to Armada 3700 SoC (ARM64)
Date: Tue, 3 May 2016 12:28:12 +0530 [thread overview]
Message-ID: <20160503065811.GP2274@localhost> (raw)
In-Reply-To: <1461916149-30900-1-git-send-email-gregory.clement@free-electrons.com>
On Fri, Apr 29, 2016 at 09:49:04AM +0200, Gregory CLEMENT wrote:
> Hi,
>
> This series adds the support of the Marvell XOR engine to the Armada
> 3700 SoC. As this SoC is an ARM64 one, then the code has been fixed to
> support the 64 bits platform.
>
> The initialization for the Armada 3700 is different from the other
> SoCs, so in order to support it, a new way of handling the different
> family have been added.
>
> Once the dmaengine part will be approved, I will apply the dts part
> in the mvebu/dt64 tree.
>
> In this fourth series I took into account the remarks from Vinoud, I
> also updated the dts patch that I will apply on my tree.
Applied, 1 thru 4.
--
~Vinod
prev parent reply other threads:[~2016-05-03 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 7:49 [PATCH v4 0/5] Add XOR engine support to Armada 3700 SoC (ARM64) Gregory CLEMENT
2016-04-29 7:49 ` [PATCH v4 1/5] dmaengine: mv_xor: make the code 64 bits compliant Gregory CLEMENT
2016-04-29 7:49 ` [PATCH v4 2/5] dmaengine: mv_xor: use SoC type instead of directly the operation mode Gregory CLEMENT
2016-04-29 7:49 ` [PATCH v4 3/5] dmaengine: mv_xor: add support for Armada 3700 SoC Gregory CLEMENT
2016-04-29 7:49 ` [PATCH v4 4/5] dmaengine: mv_xor: Allow selecting mv_xor for mvebu only compatible SoC Gregory CLEMENT
2016-04-29 7:49 ` [PATCH v4 5/5] arm64: dts: marvell: add XOR node for Armada 3700 SoC Gregory CLEMENT
2016-04-29 13:15 ` Gregory CLEMENT
2016-05-03 6:58 ` Vinod Koul [this message]
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=20160503065811.GP2274@localhost \
--to=vinod.koul@intel.com \
--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