From: Andrew Lunn Subject: Re: [PATCH 8/8] ARM: mvebu: a38x: Enable A38x XOR engine features Date: Tue, 12 May 2015 18:13:14 +0200 Message-ID: <20150512161314.GL19927@lunn.ch> References: <1431445063-20226-1-git-send-email-maxime.ripard@free-electrons.com> <1431445063-20226-9-git-send-email-maxime.ripard@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Vinod Koul , Dan Williams , Gregory Clement , Jason Cooper , Sebastian Hesselbarth , dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, Lior Amsalem , Thomas Petazzoni , Herbert Xu , "David S. Miller" To: Maxime Ripard Return-path: Received: from vps0.lunn.ch ([178.209.37.122]:50159 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932852AbbELQSL (ORCPT ); Tue, 12 May 2015 12:18:11 -0400 Content-Disposition: inline In-Reply-To: <1431445063-20226-9-git-send-email-maxime.ripard@free-electrons.com> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Tue, May 12, 2015 at 05:37:43PM +0200, Maxime Ripard wrote: > From: Lior Amsalem > > The new XOR engine has a new compatible of its own, together with new > channel capabilities. > > Use that new compatible now that we have a driver that can handle it. > > Signed-off-by: Lior Amsalem > Reviewed-by: Ofer Heifetz > Reviewed-by: Nadav Haklai > Tested-by: Nadav Haklai > --- > arch/arm/boot/dts/armada-38x.dtsi | 20 ++++++-------------- > 1 file changed, 6 insertions(+), 14 deletions(-) > > diff --git a/arch/arm/boot/dts/armada-38x.dtsi b/arch/arm/boot/dts/armada-38x.dtsi > index ed2dd8ba4080..6d07b7389415 100644 > --- a/arch/arm/boot/dts/armada-38x.dtsi > +++ b/arch/arm/boot/dts/armada-38x.dtsi > @@ -448,7 +448,7 @@ > }; > > xor@60800 { > - compatible = "marvell,orion-xor"; > + compatible = "marvell,a38x-xor"; > reg = <0x60800 0x100 > 0x60a00 0x100>; > clocks = <&gateclk 22>; > @@ -458,17 +458,13 @@ > interrupts = ; > dmacap,memcpy; > dmacap,xor; > - }; > - xor01 { > - interrupts = ; > - dmacap,memcpy; > - dmacap,xor; > - dmacap,memset; > + dmacap,pq; > + dmacap,interrupt; Does this mean the hardware only has one channel? And memset is no longer supported? Andrew > }; > }; > > xor@60900 { > - compatible = "marvell,orion-xor"; > + compatible = "marvell,a38x-xor"; > reg = <0x60900 0x100 > 0x60b00 0x100>; > clocks = <&gateclk 28>; > @@ -478,12 +474,8 @@ > interrupts = ; > dmacap,memcpy; > dmacap,xor; > - }; > - xor11 { > - interrupts = ; > - dmacap,memcpy; > - dmacap,xor; > - dmacap,memset; > + dmacap,pq; > + dmacap,interrupt; > }; > }; > > -- > 2.4.0 >