On Tuesday 24 September 2013 07:48 PM, Suman Anna wrote: > On 09/24/2013 05:24 PM, Santosh Shilimkar wrote: >> On Tuesday 24 September 2013 04:30 PM, Paul Zimmerman wrote: >>>> From: Paul Zimmerman >>>> Sent: Tuesday, September 24, 2013 1:21 PM >>>> >>>> Hi, >>>> >>>> I have an OMAP5432 uEVM which I cannot get to boot with recent mainline >>>> (tried 3.11 and 3.12-rc1). I have the TI GLSDK for this board (v6.0.0.7), >>>> which comes with 3.8.4 which works fine. >>>> >>>> I found this thread: http://marc.info/?l=fedora-arm&m=137717811815777 and >>> >>> Wrong link, should have been >>> http://marc.info/?l=linux-omap&m=137515583214350. >>> >> Its because of commit 03ab349ec{ARM: OMAP5: hwmod data: Add mailbox data} >> which >> added hwmod data but DT data for mailbox is missing. Reverting that makes >> things work. Looks like mailbox dt patches missed the last merge window. > > Yeah, the boot sequence tries to enable and idle all the hwmods, and > this results in an error while initializing the mailbox hwmod during the > sysc configuration. This is because the OMAP5 hwmod data file no longer > has the omap_hwmod_addr_space defined in the hwmod_ocp_if data. Two ways > for now to get past is either revert the mailbox hwmod commit as above > or add the DT node [2]. > Would be good if you can get the mailbox dt node in rc cycles. But since CCF is still missing if if that doesn't happen in rc's thats ok. > I will be respinning the mailbox DT series very soon targeting 3.13, so > should not be an issue when OMAP5 boot is supported directly on mainline. > Thanks
Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
