Staging Thermal FW: PCB Temp Sensor: Fix management of ADC conversion

Staging Thermal FW: PCB Temp Sensor: Fix management of ADC conversion

When an NTC thermistor is connected to the TWL6030 GPADC Channel #4,
twl6030_gpadc_conversion() function (from twl6030-gpadc driver) is
invoked.
This function stores different results into twl6030_gpadc_request
structure.
The PCB temp sensor driver shall use the ADC code instead of the
converted voltage value.
Later, the PCB temp sensor convert the ADC code into temperature
through a dedicated lookup table.

Change-Id: I1582e96035797f8c0dd6e529c65160a71e54cd6a
Signed-off-by: Sebastien Sabatier <s-sabatier1@ti.com>
ARM:OMAP4:Temp sensor: fix low limit for thresholds

ARM:OMAP4:Temp sensor: fix low limit for thresholds

As the full temperature range is -40 DegC to 125 Deg C,
this patch ensures that thresholds are higher than the low
limit (-40 Deg C) instead of 0 Deg C.

Change-Id: I28c49cd53703f9d9ed61458bc61612f4dbb476bb
Signed-off-by: Sebastien Sabatier <s-sabatier1@ti.com>
ARM:OMAP4:Temp Sensor: Define TALERT_IRQ as High level interrupt sensitive

ARM:OMAP4:Temp Sensor: Define TALERT_IRQ as High level interrupt sensitive

The thermal alert IRQ is registered as a threaded IRQ with TRIGGER_RISING and
ONESHOT flags.
This means that omap_talert_irq_handler() IRQ handler will be called upon a
rising edge of the T_ALERT (HW signal coming from HW comparison of current
temperature with hot & cold thresholds).
This means also that the irq line is disabled until the threaded handler has
been run (due to ONESHOT flag): the T_ALERT IRQ is masked at GIC level during
the threaded handler execution.
Any new thermal event occurring during the execution of the threaded handler
will not be detected. This may occur if OMAP on-die temperature variations are
fast and if the T_ALERT IRQ handler is delayed by higher priority interrupts.
Finally, the thermal governor is not informed of the new event and could
maintain incorrect constraints on CPU frequency for example.

This patch defines the TALERT_IRQ as TRIGGER_HIGH interrupt instead of
TRIGGER_RISING interrupt. Even if interrupt line is disabled during the handler
execution, HW will maintain the T_ALERT signal to high level if a second thermal
event occurs. When re-enabling the interrupt line, the omap_talert_irq_handler()
IRQ handler will be called again if needed.

Change-Id: I629d5a66702fb60b5f96773c717a2d87238dff2c
Signed-off-by: Sebastien Sabatier <s-sabatier1@ti.com>
Staging: add TI OMAP Thermal Framework drivers

backported for TUNA board by faux123

Conflicts:
	drivers/staging/Kconfig
	drivers/staging/Makefile

Conflicts:
	drivers/staging/Kconfig
	drivers/staging/Makefile
plat-omap: add compatibility with new TI OMAP thermal framework drivers
thermal framework: increase duty cycle throttle temperature from 65 to 75
omap4: add 4430 ES2.3 support

omap4: add 4430 ES2.3 support

And default to 4430 ES2.3 for unidentified silicon.

Change-Id: I06b0aa9c5f33af25345996cf9d0c994491093096
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
OMAP4: ID: Chip detection for OMAP4470

Add support for detection of the next chip in the OMAP4 family: OMAP4470 ES1.0

Change-Id: I931d3df6e69fdc3ee4a307c204a68fc9b3ff519b
Signed-off-by: Leonid Iziumtsev <x0153368@ti.com>
modified by faux123
OMAP4: Add 4430 ES2.3 chip is check

OMAP4: Add 4430 ES2.3 chip is check

4430 ES2.3 chip is check was missed during the merge
phase.

Putting it back in

Change-Id: I94fa2b8f803acb2a13c2f7db4558b2864106d213
Signed-off-by: Dan Murphy <dmurphy@ti.com>
ARM: OMAP2+: voltage: add check for missing PMIC info in VP init

If PMIC info is not available in omap_vp_init(), abort.

Signed-off-by: Abhilash K V <abhilash.kv@ti.com>
[khilman: minor subject edits]
Signed-off-by: Kevin Hilman <khilman@ti.com>
ARM: OMAP: voltage: cleanup VC/VP error messages

Cleanup formatting/spacing on a  couple multi-line error messages.

Signed-off-by: Kevin Hilman <khilman@ti.com>
ARM: 7192/1: OMAP: Fix build error for omap1_defconfig

Otherwise we get the following error:

In function 'omap_init_consistent_dma_size':
error: implicit declaration of function 'init_consistent_dma_size'

Signed-off-by: Tony Lindgren <tony@atomide.com>
Acked-by: Nicolas Pitre <nicolas.pitre@linaro.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
ARM: OMAP: Add Secure HAL and monitor mode API infrastructure.

On OMAP secure/emulation devices, certain APIs are exported by secure
code. Add an infrastructure so that relevant operations on secure
devices can be implemented using it.

While at this, rename omap44xx-smc.S to omap-smc.S since the common APIs
can be used on other OMAP's too.

Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Acked-by: Jean Pihet <j-pihet@ti.com>
Reviewed-by: Kevin Hilman <khilman@ti.com>
Tested-by: Vishwanath BS <vishwanath.bs@ti.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
Signed-off-by: Willi Ye <williye97@gmail.com>

Conflicts:
	arch/arm/mach-omap2/Makefile

Conflicts:
	arch/arm/mach-omap2/Makefile