>>-----Original Message----- >>From: Matt Singer [mailto:msinger@xxxxxxxxxxxxxx] >>Sent: Monday, August 30, 2010 6:02 PM >>To: Gopinath, Thara; linux-omap@xxxxxxxxxxxxxxx >>Subject: RE: OMAP3 Clock & CPU frequency >> >>Is it in mainline yet or still a patch? Hello Matt, It is not in mainline and is only a patch series. Link to the series http://marc.info/?l=linux-omap&m=128170725127719&w=2 Link to the specific patch http://marc.info/?l=linux-omap&m=128170725327731&w=2 Hope this helps you. One advice to you would be not to top post while replying to the mailing list. It is a bad etiquette. Regards Thara >> >>-----Original Message----- >>From: Gopinath, Thara [mailto:thara@xxxxxx] >>Sent: Monday, August 30, 2010 6:29 AM >>To: msinger@xxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx >>Subject: RE: OMAP3 Clock & CPU frequency >> >> >> >>>>-----Original Message----- >>>>From: linux-omap-owner@xxxxxxxxxxxxxxx >>>>[mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of >>>>msinger@xxxxxxxxxxxxxx >>>>Sent: Monday, August 30, 2010 12:33 AM >>>>To: linux-omap@xxxxxxxxxxxxxxx >>>>Subject: OMAP3 Clock & CPU frequency >>>> >>>> >>>>Kevin Hilman wrote: >>>> >>>>>>FWIW, the SR hwmods are still not enabling by default because the >>>>>>clock fwk fails due to missing clockdomain. >>>>>> >>>>>>I've been manually working around by adding >>>>>> >>>>>> .clkdm_name = "wkup_clkdm", >>>>>> >>>>>>to sr*_fck, but I know that's not the correct fix. >>>>>> >>>>>>Kevin >>>> >>>>That only seems to eliminate the warning. I'm seeing omap_hwmod: >>>>sr1_hwmod: cannot be enabled (3) >>>>because oh->prcm.omap2 is Null on the call to >>>>omap2_cm_wait_module_ready() >>>> >>>>cpufreq changing does not occur. >> >> >>Which version of these patches are you using? >>The V2 version does have oh->prcm.omap2 populated for smartreflex. >> >>Regards >>Thara >> >>No virus found in this incoming message. >>Checked by AVG - www.avg.com >>Version: 9.0.851 / Virus Database: 271.1.1/3093 - Release Date: 08/29/10 >>14:34:00 -- 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
