On Mon, Jan 6, 2014 at 1:57 AM, Loren Amelang <[email protected]> wrote: >> @Vaibhav, > > > Just found this: > http://web.archiveorange.com/archive/v/vEQ2y6LmBVoCWJwTbcnr > > about a problem with clocks not being enabled before mdio: probe - which > seems directly applicable to my Ubuntu fail! > > "Make the driver control the device clocks. Appearantly, the Davinci > platform probes this driver with the clock all powered up, but on OMAP, > this isn't the case.Make the driver control the device clocks. Appearantly, > the Davinci > platform probes this driver with the clock all powered up, but on OMAP, > this isn't the case." > > "Certainly, with respect to CPSW & MDIO, this patch is not enough and > requires further investigation. I have started looking at this and > hopefully will have some solution soon..." > > But that was over a year ago - was it resolved?
As per the commit logs of the mainline kernel a patch adding pm_runtime_* calls in the driver went in around 3.7-rc3. I believe the images that you have which are based on v3.8 will have them in place. I still can't think of a reason why it would worked earlier. Could be a race condition or could even be a hardware thing. Try changing the kernel build to narrow it down. And yes, the error that you see would typically come up when the init fails (typically clock). -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
