> -----Original Message----- > From: linux-omap-ow...@vger.kernel.org > [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Tony > Lindgren > Sent: Tuesday, October 20, 2009 12:02 PM > To: Kevin Hilman > Cc: Sripathy, Vishwanath; linux-omap@vger.kernel.org > Subject: Re: [RFC][Patch] OMAP3 PM: sysfs vdd_opp change to use > ConstraintFramework > > * Kevin Hilman <khil...@deeprootsystems.com> [091020 08:51]: > > "Sripathy, Vishwanath" <vishwanath...@ti.com> writes: > > > > > Sysfs entry vdd_opp currently does not use constraint framework. > > > Because of this, even if you set the opp via this entry, it has no effect > > > since it can be overridden by on demand governor any time. > > > This patch has changes to make vdd_opp to use constraint framework. > > > vdd_lock variable has to be used when application wants to disable DVFS > > > altogether. This will override any other constraints and will lock the > > > OPP to given value. > > Since we can do the equivalent with CPUFreq using the userspace > > governor, I don't see the point of having an additional interface. > > > > Comments? > > Total ack from me!
Only thing what I think of is, L3 rate. -Girish -- 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
