* Menon, Nishanth <nm@xxxxxx> [110518 11:03]: > On Wed, May 18, 2011 at 02:59, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > * Nishanth Menon <nm@xxxxxx> [110518 08:13]: > >> Kevin's patch: > >> OMAP3+: voltage: remove unneeded debugfs interface > >> > >> removed ability to check the voltages in the domains. > >> This puts a crunch on validation we can do, hence we > >> re-introduce them back in > > > >> Signed-off-by: Nishanth Menon <nm@xxxxxx> > >> --- > >> Âarch/arm/mach-omap2/voltage.c | Â 66 +++++++++++++++++++++++++++++++++++++++++ > >> Âarch/arm/mach-omap2/voltage.h | Â Â1 + > >> Â2 files changed, 67 insertions(+), 0 deletions(-) > > > > Hmm, this seems to be adding the debug code instead? > > Yes, we need some interface to know what the current voltages are for > each of the domain when verifying if dvfs is actually scaling voltage > or not. the other option is to use omapconf (not yet public and only > supports OMAP4) to see what the voltages are. Though omapconf is an > option, it shows what it's computation of voltage from vsel is, not > what the kernel internally thinks (vsel_uv functions) it is. I guess I just got confused reading the patch description.. Tony -- 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
