Revert "MPU 1350MHz: improve stability:"

This reverts commit 8ce710891999f7690b8ba6e1fcdcb761d546581f.
Revert "Added overclock to max 1.35MHz"

This reverts commit ff54f3e788861d73d4b0011bb29e54985613f8c6.
Revert "OMAP3630+: SmartReflex 1p5: remove voltage clamp down"

This reverts commit afadff82e7b2041498c95f266b76b21dda04e703.
arm: mach-omap2: opp4xxx_data: Update voltage/frequency
arm: mach-omap2: opp4xxx_data.c: 1.5GHz needs different SR ntarget
arm: mach-omap2: control.h: use a unique fuse offset fo 1.65ghz
arm: mach-omap2: dpll44xx: adjust DCC for notrim
arm: mach-omap2: omap4_trim_quirks.c: enable trim override
arm: mach-omap2: smartreflex-class1p5.c: skip calibration on notrim freqs
arm: mach-omap2: smartreflex-class1p5.c: just to complete the calibration tweak for high freq/voltage
arm: mach-omap2: omap2plus-cpufreq.c: Add voltage control
SR: Custom SR Tuning v1 - supports MPU, IVA, and CORE

Override kernel default VDDMIN via sysfs (debug fs).
/sys/kernel/debug/smartreflex/sr_*/vmin
Custom SR Tuning V2: allow SR to calibrate high voltages

For MPU only, should have zero effect on IVA and CORE
omap2plus: cpufreq: Modify lpj recalculation logic

Somethimes "mdelay" function provide delay
that several times shorter than it should be.

This happens because recalculating lpj
performed after switching OPP. In this case,
for short period of time, when OPP on MPU
was switched but lpj was not recalculated,
"udelay" function can provide incorrect
delay - upto 5 times shorter
(if OPP was switched from lowest to highest).

This patch changes lpj recalculation logic to:
if OPP will be switched to higher - recalculate lpj before switching OPP,
if OPP will be switched to lower - recalculate lpj after switching OPP.

Change-Id: I3258e756c471fd0258a849d712ab00f4e1279ea9
Signed-off-by: Sergii Postulga <x0153364@ti.com>
drivers: i2c: busses: i2c-omap.c: use usleep_range to wait instead of msleep

according to the docs msleep(1) means wait up 20ms. i2c bus probably
doesn't need to wait that long. Potential performance boost.
Added Sound Control version 1.

Conflicts:

	drivers/misc/Kconfig
	drivers/misc/Makefile
TWL6040_RAMP_ZERO is only used for changing the headset volume.
The headset power mode is kept on high-performance while no headset is
plugged in and changed to the user defined mode as soon as a headset
is plugged in.

Conflicts:

	sound/soc/codecs/twl6040.c
If headphones are (un)plugged and the codec driver has not been initialized
yet (can happen during boot with attached headphones), the headset power
mode is not changed.
Properly apply volume boost on volume change.