From: Nishanth Menon <nm@ti.com>
To: Joachim Eastwood <manabian@gmail.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, "Fernandes, Joel" <joelf@ti.com>
Subject: Re: L3 custom error on OMAP4460 (AES/DES)
Date: Mon, 14 Apr 2014 14:19:25 -0500 [thread overview]
Message-ID: <534C34BD.6060109@ti.com> (raw)
In-Reply-To: <CAGhQ9Vxp6_OvFRnd1KL+oAX3xR72vWHgiWBmoqjfSXk1DwAusg@mail.gmail.com>
On 04/14/2014 02:15 PM, Joachim Eastwood wrote:
> On 14 April 2014 15:38, Santosh Shilimkar <santosh.shilimkar@ti.com> wrote:
>> On Saturday 12 April 2014 05:06 PM, Joachim Eastwood wrote:
>>> Hi,
>>>
>>> I getting the following error on Linus master right now.
>>>
>>> [ 2.166320] WARNING: CPU: 0 PID: 0 at drivers/bus/omap_l3_noc.c:113
>>> l3_interrupt_handler+0xf4/0x154()
>>> [ 2.166320] L3 custom error: MASTER:MPU TARGET:L4 PER2
>>> [ 2.166320] Modules linked in:
[...]
>>> The hardware is a VAR-STK-OM44 dev kit. I got one patch on top of
>>> Linus master which is the DT support patch which I posted a couple of
>>> hours ago.
>>>
>> Have you tried removing AES from the build ? Probably worth a
>> try.
>
> Removing the aes driver makes the warning from omap_l3_noc disappear.
>
> I also tried tried the omap_l3_noc patches from Nishanth Menon that
> was just posted but it had the same error when the aes driver was
> built-in.
Yeah - it better :).. Good to know that driver continues to report bad
accesses by drivers to targets that are not active yet. will be great
if you could provide a "Tested-by" tag on my series :).
Btw, I just finished testing on PandaBoard ES and SDP4430 and I dont
see the error that you see on var som. I wonder why?
pandaboard-es: Boot PASS: http://slexy.org/raw/s21Hsq97mt
sdp4430: Boot PASS: http://slexy.org/raw/s2ZQJUqjrP
>
> Would it be possible for someone to add hwmod data for the aes driver
> to the kernel so that the aes could actually work?
Joel, are you planning on posting OMAP4 hwmod data for AES/DES?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-04-14 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 21:06 L3 custom error on OMAP4460 Joachim Eastwood
2014-04-14 13:38 ` Santosh Shilimkar
2014-04-14 19:15 ` Joachim Eastwood
2014-04-14 19:19 ` Nishanth Menon [this message]
[not found] ` <CAGhQ9Vz0Yj8Qz1x9tLH9=jkNEvmsrKBH2=QbYBUYUgoqxGuHAQ@mail.gmail.com>
2014-04-15 14:01 ` L3 custom error on OMAP4460 (AES/DES) Nishanth Menon
2014-04-15 15:55 ` Joachim Eastwood
2014-04-15 17:15 ` Joel Fernandes
2014-04-15 17:19 ` Nishanth Menon
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=534C34BD.6060109@ti.com \
--to=nm@ti.com \
--cc=joelf@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=santosh.shilimkar@ti.com \
/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.