DRIVERS: MISC: Add OMAP4430 Static Thermal Policy

Adding Static Thermal Policy for OMAP4430.
Added new driver module to control max opp duty cycle.

Change-Id: I9781f4db19b055eefb0a4bf28bf5f5c516307509
Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
modified for Tuna board by faux123

Conflicts:
	drivers/misc/Makefile
DRIVERS: MISC: move DC from misc to thermal_framework

We have special place for thermal framework. Duty cycle was placed
to separate place. The patch moves DC to thermal_framework place.

Change-Id: Id1e85d853df2fbbd597a5dd87e658fce58e4ae24
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
modified for TUNA by faux123

Conflicts:
	drivers/misc/Makefile
Thermal Governor: Added duty cycle governor

Add the OMAP duty cycle governor to the thermal framework.
This component will impose the policy for the PCB temp
sensor in case ondie sensor is absent.

Change-Id: I05f7272445567cf74be6f0932d7024f0d9d34dee
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
modified for TUNA board by faux123
DRIVERS: MISC: change the DC cpufreq control to TF control

Duty cycle uses sys fs to control cpufreq. It is not safe.
The user(overclocker) can burn the device using simple script that
changes max_frequency. The thermal framework has own mechanism for
this and the patch changes the duty cycle mechanism to thermal
framework variant of cpufreq control.

Change-Id: Ifc0f8b81addb7524eb67d116e4780978739a67f3
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
modified for TUNA board by faux123

Conflicts:
	arch/arm/mach-omap2/omap2plus-cpufreq.c
add missing variables and remove unused

Signed-off-by: Willi Ye <williye97@gmail.com>

Conflicts:
	arch/arm/mach-omap2/omap2plus-cpufreq.c
	drivers/gpu/pvr/pvr_governor.c
	include/linux/cpufreq.h
should have duty cycle