From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: marvell_cesa fails to register on kirkwood (88F6282)
Date: Fri, 5 Feb 2016 10:02:46 +0100 [thread overview]
Message-ID: <20160205090246.GE32272@lunn.ch> (raw)
In-Reply-To: <CAKzmTe0mvZD5UwqM47uXbM7Z7oAJpE4g4BVMba1hkzqNu+Zbgw@mail.gmail.com>
On Fri, Feb 05, 2016 at 06:01:18AM +0100, JM wrote:
> Hi,
>
> I am testing marvell_cesa on a kirkwood device (QNAP TS-212p, Marvell
> Kirkwood 88F6282, dts: http://pastebin.com/Gk95KFHf ).
> As of kernel 4.4 (4.4.0-trunk-kirkwood #1 Debian 4.4-1~exp1) it fails
> in the following way:
>
> modprobe marvell_cesa allhwsupport=1
> dmesg | tail -n 1
> [ 1057.855091] marvell-cesa: probe of f1030000.crypto failed with error -12
>
> or:
>
> modprobe marvell_cesa
> dmesg | tail -n 1
> [ 9178.399357] marvell-cesa: probe of f1030000.crypto failed with error -524
>
> With kernel 4.3 it would fail with error -22 on that hardware. There
> are scattered reports from other users experiencing the same issue
> (1,2,3)
>
> I wonder if this is a result of an invalid definition of the
> crypto-sram in the dts of this SoC, or perhaps some other problem
> (PEBKAC included).
Hi Jan
Do you have SRAM enabled in your kernel configuration. The
mvebu_v5_defconfig does not have it, which is a bug really.
Andrew
next prev parent reply other threads:[~2016-02-05 9:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 5:01 marvell_cesa fails to register on kirkwood (88F6282) JM
2016-02-05 9:02 ` Andrew Lunn [this message]
2016-02-05 10:29 ` Boris Brezillon
2016-02-05 15:00 ` JM
2016-02-05 15:45 ` Gregory CLEMENT
2016-02-05 16:01 ` JM
2016-02-05 16:09 ` Gregory CLEMENT
2016-02-05 16:28 ` Gregory CLEMENT
2016-02-05 20:41 ` Arnaud Ebalard
2016-02-05 21:04 ` Arnaud Ebalard
2016-02-06 15:14 ` JM
2016-02-06 21:57 ` Arnaud Ebalard
2016-02-08 17:23 ` Russell King - ARM Linux
2016-02-14 0:09 ` JM
2016-04-05 20:30 ` JM
2016-02-05 22:57 ` JM
2016-02-05 16:28 ` Boris Brezillon
2016-02-05 17:21 ` JM
2016-02-05 15:58 ` Fabio Estevam
2016-02-05 16:02 ` Boris Brezillon
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=20160205090246.GE32272@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.