public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: romain.perier@free-electrons•com (Romain Perier)
To: linux-arm-kernel@lists•infradead.org
Subject: [crypto] [marvell-cesa] Driver hangs on Armada 385 device
Date: Fri, 19 Aug 2016 15:07:44 +0200	[thread overview]
Message-ID: <57B704A0.4050603@free-electrons.com> (raw)
In-Reply-To: <20160819141251.5dcc835d@free-electrons.com>

Hello,

Le 19/08/2016 14:12, Thomas Petazzoni a ?crit :
> Hello,
>
> I'm adding Romain Perier in Cc, since he is actively working on the
> CESA driver.
>
> On Fri, 19 Aug 2016 14:54:50 +0300, radioconfusion at gmail.com wrote:
>
>>> On Tue, 05 Jul 2016 11:46:30 +0300, radioconfusion at gmail.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.
>>
>> I just tested the marvell-cesa with Linux 4.8-rc2 and Armada 385.
>> There is still the same hanging issue (originally described on
>> https://bugzilla.kernel.org/show_bug.cgi?id=120111).
>>
>> Please let me ask which model of Armada board has been verified to work with the
>> marvell-cesa driver?
>
> The Armada 388 GP board.

For now:
The Armada 388-DB-GP
The Armada 385-DB-AP
The Armada 375-DB


>
>> I'm using a custom board based on 88F6820. Is this SoC
>> model fully supported by the driver? Do you know if there is some necessary
>> hardware initializations which must be done on u-boot? I'm using latest Marvell
>> patch set (2015_T1.0p16) on u-boot.
>>
>> My test case have been:
>> # cryptsetup benchmark --cipher aes-cbc
>>
>> and that always freezes the board.
>
> Romain, can you test the same scenario, and see if you can reproduce
> the hang or not?

Sure,


I have did exactly the same tests with Linux 4.8-rc2 (using a rootfs 
buildroot-2016.02 over nfs) on A388-db-gp and A385-db-ap, both work just 
fine. I launched the benchmark several times.

I am running uboot, Marvell version: 2015_T1.0p5


See yourself: http://paste.ubuntu.com/23070118


Romain
-- 
Romain Perier, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-08-19 13:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 11:54 [crypto] [marvell-cesa] Driver hangs on Armada 385 device radioconfusion at gmail.com
2016-08-19 12:12 ` Thomas Petazzoni
2016-08-19 13:07   ` Romain Perier [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2016-08-24 10:52 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-07-14 12:29 radioconfusion at gmail.com
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=57B704A0.4050603@free-electrons.com \
    --to=romain.perier@free-electrons$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox