I dont' know if it helps, but I struggeled with this too. With my DM3730 (OMAP 3630), I had to enable Device Drivers->Adaptive Voltage Scaling Class Support which enables CONFIG_POWER_AVS, a requirement for POWER_AVS_OMAP. Once I did that, I was able to get AVS Class 3 working on my DM3730 using th3 4.2+ kernel. I haven't tried it with 3.14, but I would expect it to be something similar. adam On Wed, Jan 6, 2016 at 9:08 AM, Nishanth Menon <nm@xxxxxx> wrote: > On 01/06/2016 09:05 AM, Frank Jenner wrote: >> On Wed, Jan 6, 2016 at 9:26 AM, Nishanth Menon <nm@xxxxxx> wrote: >>> On 01/06/2016 08:22 AM, Frank Jenner wrote: >>>> Hello, >>>> >>>> I am working on trying to enable power management features on a >>>> product that was based on the OMAP4430 SoC and the mainline 3.14 >>>> kernel. In particular, I am interested in enabling Smart Reflex/AVS >>>> and frequency scaling (via cpufreq) functionality. >>> >>> >>> AVS class1.5 is supposed to be the official AVS class to be supported on >>> OMAP3630, OMAP4, OMAP5 SoCs. unfortunately, we dont have that supported >>> in upstream yet - let alone with cpufreq. >>> >>> -- >>> Regards, >>> Nishanth Menon >> >> Sorry my original post might have been TL;DR, but is there a public >> fork/branch that does have the support? > > > There should be TI vendor kernels on 3.0 or 3.4 kernel that should have > full entitlement of the SoC if you need that.. but I doubt there has > been work on OMAP4 on more recent kernels to my knowledge. All work on > OMAP4/3 is mostly community driven and in upstream. > > https://plus.google.com/+NishanthMenon/posts/gvyZQcNieoq > kind of gives an overview of where we need to go. all contributions are > welcome. > > -- > Regards, > Nishanth Menon > -- > 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 -- 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
