Nishanth, On 04/14/2014 02:19 PM, Nishanth Menon wrote: > On 04/14/2014 02:15 PM, Joachim Eastwood wrote: >> On 14 April 2014 15:38, Santosh Shilimkar <santosh.shilimkar@xxxxxx> 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? > I was out sick yesterday, sorry for the late reply. Yes, sure. I believe it wasn't posted due to another kernel problem which I don't remember. I'll post it this week after some more testing and rebasing. Thanks for patching the pm_runtime return to handle this. Regards, -Joel -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
