From: radioconfusion@gmail.com (radioconfusion at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [crypto] [marvell-cesa] Driver hangs on Armada 385 device
Date: Thu, 14 Jul 2016 15:29:14 +0300 [thread overview]
Message-ID: <5787859b.c3c4190a.282b0.3efb@mx.google.com> (raw)
Hello,
On Thu, 7 Jul 2016 15:43:14 +0200, thomas.petazzoni at free-electrons.com wrote:
> > > > My Armada 385 -device hangs when using marvell-cesa -driver.
> > > > I'm using Linux 4.4.10 and armada-385-db-ap.dts.
> > > > I have also tried with the driver version of Linux 4.7-rc3.
> > > >
> > > > Please see https://bugzilla.kernel.org/show_bug.cgi?id=120111 for details.
> >
> > > Can you try with
> > > http://git.infradead.org/linux-mvebu.git/commitdiff/c5379ba8fccd99d5f99632c789f0393d84a57805
> > > applied ?
> >
> > Thanks Thomas.
> > Your patch seems to fix a random hang during crypto operations.
>
> OK, great.
>
(Some lines snipped...)
> Could you test with the latest 4.7-rc kernel + the patch I provided?
Sorry about that silence. Finally I had some time for testing this.
I took Linux 4.7-rc7 (92d21ac74a9e3c09b0b01c764e530657e4c85c49) and just put "fix HW I/O coherency related deadlocks" to top of it.
Unfortunately, the result was exact same than 4.4.10.
First, without the driver:
# cryptsetup benchmark --cipher aes-cbc
# Tests are approximate using memory only (no storage IO).
# Algorithm | Key | Encryption | Decryption
aes-cbc 256b 21.9 MiB/s 23.6 MiB/s
Loading the driver:
# modprobe marvell_cesa
[ 103.213901] marvell-cesa f1090000.crypto: CESA device successfully registered
And after that:
# cryptsetup benchmark --cipher aes-cbc
was never done.
Thanks,
Jussi
next reply other threads:[~2016-07-14 12:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 12:29 radioconfusion at gmail.com [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-24 10:52 [crypto] [marvell-cesa] Driver hangs on Armada 385 device radioconfusion at gmail.com
2016-08-24 12:38 ` Thomas Petazzoni
2016-08-24 9:15 radioconfusion at gmail.com
2016-08-24 9:26 ` Russell King - ARM Linux
2016-08-19 11:54 radioconfusion at gmail.com
2016-08-19 12:12 ` Thomas Petazzoni
2016-08-19 13:07 ` Romain Perier
2016-08-19 13:08 ` Russell King - ARM Linux
2016-08-19 13:28 ` Russell King - ARM Linux
2016-08-19 14:09 ` Romain Perier
2016-08-19 14:19 ` Romain Perier
2016-08-19 14:21 ` Russell King - ARM Linux
2016-08-19 14:39 ` Romain Perier
2016-07-08 9:55 radioconfusion at gmail.com
2016-07-07 9:20 radioconfusion at gmail.com
2016-07-07 13:43 ` Thomas Petazzoni
2016-07-05 8:46 radioconfusion at gmail.com
2016-07-06 7:06 ` Thomas Petazzoni
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=5787859b.c3c4190a.282b0.3efb@mx.google.com \
--to=radioconfusion@gmail.com \
--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.