Re: [PATCH v3 02/16] crypto: add a new driver for Marvell's CESA

2015-05-27 Thread Imre Kaloz
On Mon, 25 May 2015 13:17:13 +0200, Boris Brezillon  
boris.brezil...@free-electrons.com wrote:


Sorry, I didn't word it right - the series is missing the crypto nodes  
for

the orion, 375 and 38x platforms.


I only add nodes for platforms I have tested on.
If you're able to test on those platforms I'd be happy to include those
changes in the upcoming version.


I would test on 38x but I don't have access to the cpu datasheets to fill  
in the missing pieces.. Thomas, Gregory, could one of you add those?



Imre
--
To unsubscribe from this list: send the line unsubscribe linux-crypto in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v3 14/16] ARM: marvell/dt: enable crypto on armada-xp-gp

2015-05-26 Thread Imre Kaloz
On Tue, 26 May 2015 10:59:36 +0200, Boris Brezillon  
boris.brezil...@free-electrons.com wrote:


snip

As the crypto engine really depend on the SoC itself and not of the  
board,

what about updating the dts of the other board using an Armada XP?


But that means introducing changes I haven't tested. Are you okay with
that ?


Well, worst case send it as a separate patch as RFC - I'm sure people will  
test and report back.



Cheers,

Imre
--
To unsubscribe from this list: send the line unsubscribe linux-crypto in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v3 02/16] crypto: add a new driver for Marvell's CESA

2015-05-25 Thread Imre Kaloz

Hi Boris,

On Mon, 25 May 2015 13:08:12 +0200, Boris Brezillon  
boris.brezil...@free-electrons.com wrote:



 Yep, I noticed that after submitting this version. I guess I only
 needed the import function for my test cases and thus forgot to
 implement the import function.
 Anyway, I just added the the import functions (they'll be available in
 my v4).

Given the driver is supposed to work on platforms up to 38x, could v4
include the missing bindings for those platforms, too?


Sure, what's missing ?
I already added the cesazX clocks and the marvell,armada-38x-crypto
compatible string ?



Sorry, I didn't word it right - the series is missing the crypto nodes for  
the orion, 375 and 38x platforms.


Imre
--
To unsubscribe from this list: send the line unsubscribe linux-crypto in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v3 02/16] crypto: add a new driver for Marvell's CESA

2015-05-25 Thread Imre Kaloz

Hi Boris,

On Mon, 25 May 2015 10:10:16 +0200, Boris Brezillon  
boris.brezil...@free-electrons.com wrote:


snip


Yep, I noticed that after submitting this version. I guess I only
needed the import function for my test cases and thus forgot to
implement the import function.
Anyway, I just added the the import functions (they'll be available in
my v4).


Given the driver is supposed to work on platforms up to 38x, could v4  
include the missing bindings for those platforms, too?



Thanks,

Imre
--
To unsubscribe from this list: send the line unsubscribe linux-crypto in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html