[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1501132330460.28034@utopia.booyaka.com>
Date: Tue, 13 Jan 2015 23:45:09 +0000 (UTC)
From: Paul Walmsley <paul@...an.com>
To: Suman Anna <s-anna@...com>
cc: Lokesh Vutla <lokeshvutla@...com>, Roger Quadros <rogerq@...com>,
tony@...mide.com, santosh.shilimkar@...cle.com, t-kristo@...com,
nm@...com, nsekhar@...com, bcousson@...libre.com,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: hwmod: Fix _wait_target_ready() for hwmods
without sysc
Hi Suman
On Tue, 6 Jan 2015, Suman Anna wrote:
> Looking at your rc3 log @
> http://www.pwsan.com/omap/testlogs/test_v3.19-rc3/20150105224749/boot/4460varsomom/,
> I do see a missing reg entry for mailbox, and that's the reason for your
> hang because of the missing bail out in your new patch.
>
> [ 0.261932] ------------[ cut here ]------------
> [ 0.261962] WARNING: CPU: 0 PID: 1 at
> arch/arm/mach-omap2/omap_hwmod.c:2458 _init+0x3a0/0x3f0()
> [ 0.261962] omap_hwmod: mailbox: doesn't have mpu register target base
> ...
> ...
> [ 0.262329] ---[ end trace a1be72591db4662e ]---
>
> Now that said, this is weird, since the reg property for mailbox is
> defined in the base omap4.dtsi and should be inherited by the 4460
> VAR-SOM-OM, unless you are booting with an old dtb.
Yeah, it doesn't make sense. I'm pretty sure I'm using the right DTB
here, since that board is booting with a concatenated uImage + DTB.
Well, at least there's a good test platform here.
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists