[PATCH] ARM: configs: Enabling the new Marvell's cryptographic engine driver for mvebu_v7_defconfig

[Gregory CLEMENT]

(adding Jason Cooper in CC:)

Hi Thomas and Andrew
 
 On ven., mars 18 2016, Thomas Petazzoni <thomas.petazzoni at free-electrons.com> wrote:

> Hello,
>
> On Fri, 18 Mar 2016 14:14:32 +0100, Andrew Lunn wrote:
>
>> Isn't this also applicable to mvebu v5?
>> 
>> And your change to multi_v7_defconfig could also be applied to
>> multi_v5_defconfig.
>
> mvebu_v5 already enables a crypto driver, but it's the old one. So
> there's a decision to be taken here whether we move all the platforms
> to use the new driver or not.
>
> The new driver has been tested on the Armada family, and I believe also
> on Kirkwood. However I'm pretty sure it hasn't been tested on Dove and
> Orion.
>
> Dove is ARMv7 and enabled in mvebu_v7_defconfig, but since neither the
> old nor the new driver were enabled in mvebu_v7_defconfig, we are not
> going to disrupt any existing user here by adding the new driver in the
> defconfig.
>
> Changing mvebu_v5_defconfig, multi_v5_defconfig, orion5x_defconfig and
> dove_defconfig however implies moving those defconfigs away from the
> old driver, and select the new one instead. A more serious change,
> IMO.


For Dove I don't know if there are users for this module, but for Orion
and Kirkwood as they are used in NAS product, I am pretty sure that
people use it. I would like to have some feedback about users which have
switched to the new driver. I think Jason did it on kirkwood.

Gregory


>
> Best regards,
>
> Thomas
> -- 
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com