Re: OMAP4430 power management support
On 01/06/2016 01:44 PM, Adam Ford wrote: > Any chance you can define what you mean by 'issues' and 'old'? > AVS class recommendation is AVS Class 1.5 for DM3730. If one does not follow the recommendation, then the result will be that some devices may not function OR fail in some unpredictable manner after a duration of time (aka device gets old). > Logic PD (my daytime employer) uses AVS 3 in their custom Linux > distribution. If that's going to be a problem, I would like to notify > some people there. Logic PD probably should talk with TI on the topic. -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4430 power management support
Any chance you can define what you mean by 'issues' and 'old'? Logic PD (my daytime employer) uses AVS 3 in their custom Linux distribution. If that's going to be a problem, I would like to notify some people there. adam On Wed, Jan 6, 2016 at 1:12 PM, Nishanth Menon wrote: > On 01/06/2016 10:02 AM, Adam Ford wrote: >> 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 > > > Arggh... using AVS class3 with DM3730 will create all kinds of issues > later on as the device gets old. Wish we had managed to get AVS 1.5 > basic functionality upstream :(. > > > -- > Regards, > Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4430 power management support
On 01/06/2016 10:02 AM, Adam Ford wrote: > 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 Arggh... using AVS class3 with DM3730 will create all kinds of issues later on as the device gets old. Wish we had managed to get AVS 1.5 basic functionality upstream :(. -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4430 power management support
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 wrote: > On 01/06/2016 09:05 AM, Frank Jenner wrote: >> On Wed, Jan 6, 2016 at 9:26 AM, Nishanth Menon 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 majord...@vger.kernel.org > 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4430 power management support
On 01/06/2016 09:05 AM, Frank Jenner wrote: > On Wed, Jan 6, 2016 at 9:26 AM, Nishanth Menon 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4430 power management support
On Wed, Jan 6, 2016 at 9:26 AM, Nishanth Menon 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? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4430 power management support
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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
OMAP4430 power management support
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. I have attempted to use the following kernel configuration additions: CONFIG_CPU_FREQ CONFIG_POWER_AVS_OMAP CONFIG_ARM_OMAP2PLUS_CPUFREQ or CONFIG_GENERIC_CPUFREQ_CPU0 CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE CONFIG_CPU_FREQ_GOV_COMMON CONFIG_CPU_FREQ_GOV_CONSERVATIVE CONFIG_CPU_FREQ_GOV_ONDEMAND CONFIG_CPU_FREQ_GOV_PERFORMANCE CONFIG_CPU_FREQ_GOV_POWERSAVE CONFIG_CPU_FREQ_GOV_USERSPACE CONFIG_CPU_FREQ_STAT CONFIG_POWER_AVS_OMAP_CLASS3 However, I don't get the expected sysfs nodes for cpufreq, and omapconf (via "omapconf show sr") reports "All Smart-Reflex Modules disabled." During kernel boot, I also see the following output which might or might not be related to the problem: ARM PMU: not yet supported on OMAP4430 due to missing CTI driver OMAP4 PM: u-boot >= v2012.07 is required for full PM support sr_init: No PMIC hook to init smartreflex sr_init: platform driver register failed for SR In addition, if I attempt to use CONFIG_GENERIC_CPUFREQ_CPU0 instead of CONFIG_ARM_OMAP2PLUS_CPUFREQ, I also get the following output: cpufreq_cpu0: failed to get cpu0 regulator: -19 cpufreq_cpu0: failed to get cpu0 clock: -2 cpufreq-cpu0: probe of cpufreq-cpu0.0 failed with error -2 I have also tried out the latest in the linux-3.14.y branch of the ti-linux-kernel fork [1], thinking that OMAP power management might be better supported there, but similarly did not see any indication of cpufreq or Smart Reflex functioning. My question, then, is whether power management is expected to work for OMAP4430 under Linux 3.14, or whether there might be issues on my end? Perhaps I am missing something in the device tree, or maybe my bootloader isn't setting up something the kernel expects (I'm using a pretty minimal custom bootloader). If OMAP4 power management is not supported in the mainline or TI 3.14 kernels, is there another/later kernel that has this support? I was hoping to stick with 3.14 because I don't want regressions in the project due to major kernel updates, but I would be willing to see what happens with a newer kernel if it supports power management. I had been looking at a few older threads ([2], [3], [4]) that deal with this, but it was unclear whether/when such support was upstreamed. Thank you. [1] https://git.ti.com/ti-linux-kernel/ti-linux-kernel/commits/linux-3.14.y [2] http://www.spinics.net/lists/linux-omap/msg102038.html [3] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-November/212472.html [4] https://bugzilla.kernel.org/show_bug.cgi?id=58541 ___ Frank Jenner -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
