From: Suman Anna <s-anna@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Minor OMAP DTS fixes
Date: Fri, 25 Apr 2014 12:14:48 -0500 [thread overview]
Message-ID: <535A9808.70204@ti.com> (raw)
In-Reply-To: <20140425165739.GF20807@atomide.com>
Tony,
On 04/25/2014 11:57 AM, Tony Lindgren wrote:
> * Suman Anna <s-anna@ti.com> [140422 15:24]:
>> Hi Tony, Benoit,
>>
>> This series includes couple of minor fixes in the OMAP DTS files. The patches
>> are based on 3.15-rc2.
>>
>> The first patch fixes the only WARN_ON trace present during kernel boot on
>> OMAP5 uEVM, and this has been present since some time now.
>> [ 0.045578] ------------[ cut here ]------------
>> [ 0.045598] WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2538 _init+0x1c0/0x3dc()
>> [ 0.045605] omap_hwmod: mailbox: doesn't have mpu register target base
>> [ 0.045611] Modules linked in:
>> [ 0.045625] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.15.0-rc2-00001-gb5e85a0 #45
>> [ 0.045653] [<c0015724>] (unwind_backtrace) from [<c00120f4>] (show_stack+0x10/0x14)
>> [ 0.045672] [<c00120f4>] (show_stack) from [<c05a1ccc>] (dump_stack+0x78/0x94)
>> [ 0.045686] [<c05a1ccc>] (dump_stack) from [<c0042a74>] (warn_slowpath_common+0x6c/0x8c)
>> [ 0.045698] [<c0042a74>] (warn_slowpath_common) from [<c0042b28>] (warn_slowpath_fmt+0x30/0x40)
>> [ 0.045710] [<c0042b28>] (warn_slowpath_fmt) from [<c0803b40>] (_init+0x1c0/0x3dc)
>> [ 0.045724] [<c0803b40>] (_init) from [<c0029c8c>] (omap_hwmod_for_each+0x34/0x5c)
>> [ 0.045736] [<c0029c8c>] (omap_hwmod_for_each) from [<c08042b0>] (__omap_hwmod_setup_all+0x24/0x40)
>> [ 0.045748] [<c08042b0>] (__omap_hwmod_setup_all) from [<c00088b8>] (do_one_initcall+0x34/0x160)
>> [ 0.045761] [<c00088b8>] (do_one_initcall) from [<c07f7bf4>] (kernel_init_freeable+0xfc/0x1c8)
>> [ 0.045772] [<c07f7bf4>] (kernel_init_freeable) from [<c059c4f4>] (kernel_init+0x8/0xe4)
>> [ 0.045784] [<c059c4f4>] (kernel_init) from [<c000eaa8>] (ret_from_fork+0x14/0x2c)
>> [ 0.045826] ---[ end trace c25fc521f2569d3c ]---
>>
>> The last patch eliminates the following traces on AM3517 based boards.
>> [ 0.418496] platform iva.2: Cannot lookup hwmod 'iva'
>> [ 0.454352] platform 48094000.mailbox: Cannot lookup hwmod 'mailbox'
>> [ 0.460610] platform 480bd400.mmu: Cannot lookup hwmod 'mmu_isp'
>> [ 0.464065] platform 480c9000.smartreflex: Cannot lookup hwmod 'smartreflex_mpu_iva'
>>
>> There are a few other such traces remaining, but these are all on valid nodes.
>> [ 0.420275] platform 480c5000.aes: Cannot lookup hwmod 'aes'
>> [ 0.462403] platform 480c3000.sham: Cannot lookup hwmod 'sham'
>> [ 0.463246] platform 480cb000.smartreflex: Cannot lookup hwmod 'smartreflex_core'
>> [ 0.477243] platform 480ab000.usb_otg_hs: Cannot lookup hwmod 'usb_otg_hs'
>
> Thanks applying all three into omap-for-v3.15/fixes-v2 with patch
> updated with the above warnings. Next time, please include the
> warnings into the patch description, just leave out the time
> stamps.
Thanks. I have mentioned the warning for the OMAP5 one very briefly, and
wasn't sure if I needed to copy the entire backtrace, but will remember
to include them in the future.
regards
Suman
prev parent reply other threads:[~2014-04-25 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 22:23 [PATCH 0/3] Minor OMAP DTS fixes Suman Anna
2014-04-22 22:23 ` [PATCH 1/3] ARM: dts: OMAP5: Add mailbox dt node to fix boot warning Suman Anna
2014-04-22 22:23 ` [PATCH 2/3] ARM: dts: OMAP2: Fix interrupts for OMAP2420 mailbox Suman Anna
2014-04-22 22:23 ` [PATCH 3/3] ARM: dts: AM3517: Disable absent IPs inherited from OMAP3 Suman Anna
2014-04-25 16:57 ` [PATCH 0/3] Minor OMAP DTS fixes Tony Lindgren
2014-04-25 17:14 ` Suman Anna [this message]
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=535A9808.70204@ti.com \
--to=s-anna@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).