All of lore.kernel.org
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: configs: Enabling the new Marvell's cryptographic engine driver for mvebu_v7_defconfig
Date: Fri, 18 Mar 2016 15:30:59 +0100	[thread overview]
Message-ID: <20160318143059.GD8005@lunn.ch> (raw)
In-Reply-To: <20160318145131.76ffa0e1@free-electrons.com>

On Fri, Mar 18, 2016 at 02:51:31PM +0100, Thomas Petazzoni 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.

I don't know crypto to well. Is there a good test case? Something
simple to setup and run. I can test on kirkwood and Dove using the
hardware i have.

	 Andrew

  parent reply	other threads:[~2016-03-18 14:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  8:12 [PATCH] ARM: configs: Enabling the new Marvell's cryptographic engine driver for mvebu_v7_defconfig Romain Perier
2016-03-18 13:14 ` Andrew Lunn
2016-03-18 13:51   ` Thomas Petazzoni
2016-03-18 14:26     ` Gregory CLEMENT
2016-03-18 14:46       ` Russell King - ARM Linux
2016-03-18 15:35         ` Thomas Petazzoni
2016-03-18 15:45           ` Russell King - ARM Linux
2016-03-18 15:52             ` Thomas Petazzoni
2016-03-18 16:22               ` Russell King - ARM Linux
2016-03-19 17:48       ` Jason Cooper
2016-03-18 14:30     ` Andrew Lunn [this message]
2016-03-18 15:05       ` Romain Perier
2016-03-18 15:18       ` Russell King - ARM Linux
2016-03-18 15:37         ` Thomas Petazzoni
2016-03-18 14:21 ` Gregory CLEMENT

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=20160318143059.GD8005@lunn.ch \
    --to=andrew@lunn.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.