Nishant, On 04/09/2014 04:15 PM, Nishanth Menon wrote: > On 04/09/2014 07:41 AM, Nishanth Menon wrote: >> Hi, >> http://slexy.org/raw/s2pkLsiFBX >> >> I noticed the following sets of warnings with omap2plus_defconfig on >> next-20140409. As per older logs, next-20140401 had it and v3.14 tag >> also had it (I have'nt retained older logs). >> > > Here is a quick list of 20 odd boards I am testing with: > > next-20140409-omap2plus_defconfig > > 1: am335x-evm: Boot PASS: http://slexy.org/raw/s2Ho7WPbaZ > omap_hwmod: tptc* using broken dt data from edma > platform 49000000.edma: alias fck already exists > > 2: am335x-sk: Boot PASS: http://slexy.org/raw/s2A5ZJjsuZ > same for tptc, edma > > 3: am3517-evm: Boot PASS: http://slexy.org/raw/s20q8rTwCJ > omap_hwmod: mcbsp2_sidetone using broken dt data from mcbsp > omap_hwmod: usb_host_hs: could not associate to clkdm l3_init_clkdm > Address Hole seen by USB_OTG at address dc0f9c0c > platform iva.2: Cannot lookup hwmod 'iva' > platform 480c5000.aes: Cannot lookup hwmod 'aes' > platform 48094000.mailbox: Cannot lookup hwmod 'mailbox' > platform 480bd400.mmu: Cannot lookup hwmod 'mmu_isp' > platform 480c3000.sham: Cannot lookup hwmod 'sham' > platform 480cb000.smartreflex: Cannot lookup hwmod 'smartreflex_core' > platform 480cb000.smartreflex: Cannot lookup hwmod 'smartreflex_iva' > edma-dma-engine: probe of edma-dma-engine.0 failed with error -5 > > 4: am37x-evm: Boot PASS: http://slexy.org/raw/s21kcHKdyf > nothing interesting. > > 5: am43xx-epos: Boot PASS: http://slexy.org/raw/s210geZKgS > platform 53701000.des: Cannot lookup hwmod 'des' > platform 49000000.edma: alias fck already exists > the usb and qspi issue reported. > > 6: am43xx-gpevm: Boot FAIL: http://slexy.org/raw/s20t5JOyI4 > known issue. (gpio reset for DDR) > > 7: BeagleBoard-XM: Boot PASS: http://slexy.org/raw/s2TXdBONNI > omap_hwmod: mcbsp2_sidetone using broken dt data from mcbsp > omap_hwmod: mcbsp3_sidetone using broken dt data from mcbsp > omap_hwmod: usb_host_hs: could not associate to clkdm l3_init_clkdm > omap_hwmod: usb_tll_hs: could not associate to clkdm l3_init_clkdm these 2 usb host/tll messages seem to appear for all OMAP3 based boards. Seems like incorrect hwmod data. I'll send a patch to fix this. cheers, -roger -- 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
