Thread (10 messages) 10 messages, 2 authors, 2013-12-06
STALE4609d REVIEWED: 4 (4M)

[PATCH] ARM: OMAP2+: Fix populating the hwmod data from device tree

From: paul@pwsan.com (Paul Walmsley)
Date: 2013-12-06 00:07:50
Also in: linux-omap

On Thu, 5 Dec 2013, Tony Lindgren wrote:
* Tony Lindgren [off-list ref] [131121 12:49]:
quoted
* Tony Lindgren [off-list ref] [131120 17:46]:
quoted
* Tony Lindgren [off-list ref] [131120 16:06]:
quoted
They at least had interrupts listed looking at commit 3b9b10. Probably
the thing to do for now is to revert those changes, and see if we can
just remove the L3 entries from the .dtsi files.
Actually the patch I posted should be able to handle also the
ti,hwmods = "l3_main_1", "l3_main_2", "l3_main_3" property in omap4.dtsi,
but we're not currently parsing that as we only look at the children
and not the properties of the OCP bus. Should be fixable, will take a look
tomorrow if this approach makes sense to you.
OK this one seems to do the right thing for me.
No comments? I'll queue the patch below to the fixes, please yell
if you see any issues with that.
Looks reasonable to me based on a quick glance:

Acked-by: Paul Walmsley <paul@pwsan.com>

Have not tested it though.

I like the warning message for the bad data.


- Paul
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help