[crypto] [marvell-cesa] Driver hangs on Armada 385 device

Hello,

On Wed, Aug 24, 2016 at 10:26:47PM +0100, Russell King - ARM Linux wrote:

quoted

The problem caused by my mistake, I was using the following kernel parameter:
mem=1048448k

Try mem=1046M - reducing it by 2MB.  If that works, try mem=1047M
instead.  Yes, that's more than you want to reserve, but please
check how the system behaves with these.

I assume that you mean mem=1022M.

Quick testing results:
mem=256M works
mem=384M not
mem=524160k not (512M-128k)
mem=524228k works (512M-60k)
mem=512M works
mem=524348k not (512M+60k)
mem=524416k not (512M+128k)
mem=768M works
mem=896M not
mem=960M not
mem=1022M not
mem=1023M not
mem=1048000k not
mem=1048448k not (1024M-128k)
mem=1048514k not
mem=1048516k works (1024M-60k)
mem=1048518k works
mem=1048520k works
mem=1024M works

So I can reserve 0-60 kiB or 256 MiB but nothing between.
The device boots up with all listed values but cesa works with few
values only.

Best Regards
Jussi

Hello,

On Wed, 24 Aug 2016 13:52:33 +0300, radioconfusion at gmail.com wrote:

I assume that you mean mem=1022M.

Quick testing results:
mem=256M works
mem=384M not
mem=524160k not (512M-128k)
mem=524228k works (512M-60k)
mem=512M works
mem=524348k not (512M+60k)
mem=524416k not (512M+128k)
mem=768M works
mem=896M not
mem=960M not
mem=1022M not
mem=1023M not
mem=1048000k not
mem=1048448k not (1024M-128k)
mem=1048514k not
mem=1048516k works (1024M-60k)
mem=1048518k works
mem=1048520k works
mem=1024M works

The Mbus windows need to have a power of two size, and there are
windows going from the device to the CPU for devices doing DMA. If the
memory size is not a power of two, I'm not sure we're rounding up the
window size to the next power of two. That might be the issue here.

Best regards,

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