From: radioconfusion at gmail.com <hidden> Date: 2016-08-19 11:54:50
Hello,
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? 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.
Best Regards
Jussi
From: Thomas Petazzoni <hidden> Date: 2016-08-19 12:12:51
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:
quoted
On Tue, 05 Jul 2016 11:46:30 +0300, radioconfusion at gmail.com wrote:
quoted
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.
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?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://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:
quoted
quoted
On Tue, 05 Jul 2016 11:46:30 +0300, radioconfusion at gmail.com wrote:
quoted
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
quoted
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
From: linux@armlinux.org.uk (Russell King - ARM Linux) Date: 2016-08-19 13:08:46
On Fri, Aug 19, 2016 at 02:12:51PM +0200, Thomas Petazzoni wrote:
Hello,
I'm adding Romain Perier in Cc, since he is actively working on the
CESA driver.
4.7 here on Clearfog (Armada 388):
# cryptsetup benchmark --cipher aes-cbc
# Tests are approximate using memory only (no storage IO).
# Algorithm | Key | Encryption | Decryption
aes-cbc 256b 67.1 MiB/s 68.3 MiB/s
/proc/interrupts:
CPU0 CPU1
42: 2144 0 GIC-0 51 Level f1090000.crypto
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
From: linux@armlinux.org.uk (Russell King - ARM Linux) Date: 2016-08-19 13:28:45
On Fri, Aug 19, 2016 at 02:08:46PM +0100, Russell King - ARM Linux wrote:
On Fri, Aug 19, 2016 at 02:12:51PM +0200, Thomas Petazzoni wrote:
quoted
Hello,
I'm adding Romain Perier in Cc, since he is actively working on the
CESA driver.
4.7 here on Clearfog (Armada 388):
# cryptsetup benchmark --cipher aes-cbc
# Tests are approximate using memory only (no storage IO).
# Algorithm | Key | Encryption | Decryption
aes-cbc 256b 67.1 MiB/s 68.3 MiB/s
/proc/interrupts:
CPU0 CPU1
42: 2144 0 GIC-0 51 Level f1090000.crypto
With the coherency fix commit reverted (as mentioned in the bug report)
I get:
# cryptsetup benchmark --cipher aes-cbc
# Tests are approximate using memory only (no storage IO).
# Algorithm | Key | Encryption | Decryption
aes-cbc 256b 65.8 MiB/s 67.1 MiB/s
so not that different from before. Run more than 10 times without issue.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
I have also uploaded the zImage and a separated DTB (the cesa directory
can be read from your browser)
Romain
--
Romain Perier, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
I assume you mean Thomas rather than myself, as I have only Clearfog
platforms, which are all Armada 388.
I don't use uImage anymore, except with versions of uboot that are
unable to support zImage booting. Where zImage booting is supported,
I'm always using a separated DTB. Doing otherwise is insane IMHO.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
I assume you mean Thomas rather than myself, as I have only Clearfog
platforms, which are all Armada 388.
Yep, sorry. I meant, the person who has issues with cesa, i.e
radioconfusion at gmail.com :)
I don't use uImage anymore, except with versions of uboot that are
unable to support zImage booting. Where zImage booting is supported,
I'm always using a separated DTB. Doing otherwise is insane IMHO.
That's just, we have several ways to boot our Marvell devices, including
legacy or non legacy boots, uImage and zImage. Anyway,
that's not the point of my previous email.
Romain
--
Romain Perier, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com