From: Vinod Koul <vinod.koul@intel.com>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: dmaengine@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Nadav Haklai <nadavh@marvell.com>,
Lior Amsalem <alior@marvell.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Romain Perier <romain.perier@free-electrons.com>,
Omri Itach <omrii@marvell.com>, Marcin Wojtas <mw@semihalf.com>
Subject: Re: [PATCH v3 3/5] dmaengine: mv_xor: add support for Armada 3700 SoC
Date: Tue, 26 Apr 2016 22:07:58 +0530 [thread overview]
Message-ID: <20160426163758.GP2274@localhost> (raw)
In-Reply-To: <1460652818-14647-4-git-send-email-gregory.clement@free-electrons.com>
On Thu, Apr 14, 2016 at 06:53:36PM +0200, Gregory CLEMENT wrote:
> From: Marcin Wojtas <mw@semihalf.com>
>
> Armada 3700 SoC comprise a single XOR engine compliant with the ones used
> in older Marvell SoC's like Armada XP or 38x. The only thing that needs
> modification is the Mbus configuration, which has to be done on two
> levels: global and in device. The first one is inherited from the
> bootlader. The latter can be opened in a default way, leaving
s/bootlader/bootloader
> arbitration to the bus controller. Hence filled mbus_dram_target_info
> structure is not needed.
>
> Patch "dmaengine: mv_xor: optimize performance by using a subset
> of the XOR channels" introduced limitation for using XOR engines and
> channels vs number of available CPU's. Those contstraints do not however
s/contstraints/constraints
--
~Vinod
next prev parent reply other threads:[~2016-04-26 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 16:53 [PATCH v3 0/5] Add XOR engine support to Armada 3700 SoC (ARM64) Gregory CLEMENT
2016-04-14 16:53 ` [PATCH v3 1/5] dmaengine: mv_xor: make the code 64 bits compliant Gregory CLEMENT
2016-04-26 16:33 ` Vinod Koul
2016-04-14 16:53 ` [PATCH v3 2/5] dmaengine: mv_xor: use SoC type instead of directly the operation mode Gregory CLEMENT
2016-04-14 16:53 ` [PATCH v3 3/5] dmaengine: mv_xor: add support for Armada 3700 SoC Gregory CLEMENT
2016-04-26 16:37 ` Vinod Koul [this message]
2016-04-14 16:53 ` [PATCH v3 4/5] dmaengine: mv_xor: Allow selecting mv_xor for mvebu only compatible SoC Gregory CLEMENT
2016-04-14 16:53 ` [PATCH v3 5/5] arm64: dts: marvell: add XOR node for Armada 3700 SoC Gregory CLEMENT
2016-04-26 3:35 ` Vinod Koul
2016-04-26 7:28 ` Thomas Petazzoni
2016-04-26 16:32 ` 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=20160426163758.GP2274@localhost \
--to=vinod.koul@intel.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=omrii@marvell.com \
--cc=robh+dt@kernel.org \
--cc=romain.perier@free-electrons.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.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