On Fri, Feb 10, 2012 at 07:10:06AM +0000, Hiremath, Vaibhav wrote: > On Fri, Feb 10, 2012 at 07:49:47, Paul Walmsley wrote: > > > > Kevin and I just doublechecked OMAP37xx BeagleBoard xM here with Tony's > > testing branch; it works. > > > > I tried it on AM37x EVM, it did worked for me but I have some observations,
... > 2) Missing clockdomain in usb clock - > > [root@arago /]# dmesg | grep -ir hwmod > [ 0.114868] omap_hwmod: usbtll_fck: missing clockdomain for usbtll_fck. > ... I also see this on am37x evm, am35x evm, craneboard, and xM Rev B with an omap2plus_defconfig build from the testing-omap-fixes branch. > 3) Not sure how this can be handled, since from TWL regulator output > perspective it is NA. I enabled DUMMY_REGILATOR option and tried it, > it works. > > > [root@arago /]# dmesg | grep -ir fail > [ 0.166717] dpll3_m2_clk rate change failed: -22 > [ 0.828521] sharp_ls_panel display0: failed to set lcd brightness > [ 1.672454] smsc911x smsc911x.0: Failed to get supply 'vdd33a': -19 I posted a patch to address the smsc911x issue. It's a board specific fixed regulator that's controlled via a TWL GPIO but defaults to on. See [PATCH] omap: board-omap3evm: add required smsc911x regulators -Matt -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
