* Olof Johansson <olof@xxxxxxxxx> [131107 11:48]: > On Thu, Nov 7, 2013 at 11:45 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > * Kevin Hilman <khilman@xxxxxxxxxx> [131107 10:53]: > >> > >> A bunch of DT boot failures on OMAP3 platforms with latest mainline were > >> bisected down to this patch. Boot results here: > >> http://lists.linaro.org/pipermail/kernel-build-reports/2013-November/000954.html > >> > >> This doesn't seem to properly handle the OMAP3 case where we have DT > >> nodes, but no reg or interrupts properties since they're still using > >> hwmod. > >> > >> The problems seems to be because these OMAP3 platforms don't list any > >> interrupts in their DTS files for the UARTs, but a quick hack at adding > >> interrupts to omap3.dtsi didn't help either so something else is going > >> on. > >> > >> This patch should probably be reverted until it gets broader testing. > > > > Hmm I'm not seeing this with my tree, and sounds like it should be > > already fixed by commit d7c8f2596 (ARM: dts: Add missing reg, > > interrupt and dma entries for omap3). > > > > Can you check that you have that commit in your tree? > > Ah, that explains why we haven't seen it in -next. Yeah looks like there's a dependency that I missed. I probably tested the serial patch separately with omap4 only. > We should probably queue up our branches for Linus to merge ASAP, > that'll take care of it. Yeah. This issue should be of limited damage as most omap3 boards are not DT only yet, that won't happen until for v3.14. Regards, Tony -- 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
