Rajendra Nayak <[email protected]> writes: > Hi Kevin, > > On Wednesday 08 August 2012 10:48 PM, Kevin Hilman wrote: >>> The 4430 OPP table was being registered for all other OMAP4 variants >>> > too, like 4460 and 4470 causing issues with cpufreq driver >>> > enabled. 4460 and 4470 devices have different OPPs as compared to >>> > 4430, and they should be populated seperately. As long as that >>> > happens, let the OPP table registeration happen only on 4430 device. >>> > >>> > Signed-off-by: Rajendra Nayak<[email protected]> >> Thanks, adding to PM fixes for v3.6-rc (branch: for_3.6/fixes/pm) > > I just posted a v2 of this series addressing the issues raised by > Santosh on Patch 1/2. The problem with taking just $subject fix (or > taking it before Patch 1/2) is that you would hit the issue fixed > by the Patch 1/2 and cause a crash on non-4430 based OMAP4 devices with > cpufreq enabled.
OK, thanks for the warning. I'll be sure to keep them together. Kevin -- 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
