[rowboat] Re: Setting mpurate to 1000 does not work

Hi Ayoub,

You might want to check what exactly you're getting in dmesg. As far
as I can tell, setting mpurate in 2.6.37 (which is what is in devkit
2.1 gingerbread 2.3.4), has no effect that I can detect. For example,
I wanted to downclock to 400MHz and I see the kernel go:

# dmesg|grep -i mpu
[ 0.000000] Kernel command line: console=ttyO2,115200n8
androidboot.console=ttyO2 mem=256M init=/init mpurate=400 vram=8M
omapfb.vram=0:8M omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw
rootfstype=ext3 rootwait
[ 0.000000] Clocking rate (Crystal/Core/MPU): 26.0/664/600 MHz
[ 0.000000] Switched to new clocking rate (Crystal/Core/MPU):
26.0/664/400 MHz
[ 4.827789] platform mpu.0: omap_voltage_scale: Already at the
requestedrate 1000000000
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 998.36
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

So it would appear we seem to always be in 1GHz mode even though it
says switched to new clocking rate 400MHz as something else comes back
and switches it to 1GHz. I posted this question on TI's e2e site as
well. http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/t/162530.aspx#591676
Hopefully someone knowledgeable can clarify.