Up Vivid cpu freq table to 1512000

[homeslice976]

By default, the Vivid variant of the Holiday is capped at 1.2ghz, while the Raider and the Velocity are capped at 1.5ghz. This bumps the table that is used by the Vivid to 1.5ghz (copied from the _nom table)

[h8rift]

Thanks homeslice, we may have to make adjustments to it so this only occurs
on holiday (ifdefs or what not). But thanks for the work on thisbtonget the
correct clock and UV settings :-)
On Jan 31, 2013 9:15 AM, "homeslice976" notifications@github.com wrote:

By default, the Vivid variant of the Holiday is capped at 1.2ghz, while
the Raider and the Velocity are capped at 1.5ghz. This bumps the table that

is used by the Vivid to 1.5ghz (copied from the _nom table)

You can merge this Pull Request by running

git pull https://github.com/homeslice976/android_kernel_htc_msm8660 newbranch

Or view, comment on, or merge it at:

#1
Commit Summary

• CPU freq now to 1512000, as it should be. Also a slight UV

File Changes

• M arch/arm/mach-msm/acpuclock-8x60.chttps://github.com/Up Vivid cpu freq table to 1512000  #1/files#diff-0(44)

Patch Links:

https://github.com/htc-msm8660/android_kernel_htc_msm8660/pull/1.patch

• https://github.com/htc-msm8660/android_kernel_htc_msm8660/pull/1.diff

[homeslice976]

Absolutely - change what you need. I had users running this way on all variants for a few weeks and there didn't seem to be any trouble, and users who were on the Raider/Velocity did not report anything out of the ordinary - but I'm happy to let the experts clean it up any way necessary!