serial_core: used uninitialized termios when port-tty is unset

There is no reason to pass the termios struct to the
uport->ops->set_termios() when it is filled with zeros.

It leads to corruption of uart registers.

Change-Id: I2cc2c07c3ada6caf35b93d69ac9949b99ca145a5
Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
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>
TI TFW: omap die governor:fix for staying in PANIC zone

the OMAP4470 more heats up. The patch adds timer which
helps to avoid staying in PANIC zone too long time.

patch realises following algorithm

1. panic_zone_reached == 1;
2. schedule work to be executed after 2s;
3. scheduled work will cancelled if zone will be changed through 2s;
4. after 2s executes scheduled work
5. panic_zone_reached == 2;
6. schedule work to be executed after 4s relative to point 1
7. etc

Change-Id: Ide8bd588b0bf504e2378b5a655fefdeee51c90b1
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
OMAP4 CPU Thermal governor:removes repetitive info

The thermal governor prints info after each crossing of a thermal treshold.
Often treshold is crossed but thermal zone was not changed. The printed info
to clogs a console and dosen't give an effective information. The patch
removes repetitive info for all zone except for the panic zone. The
panic zone is critical and a duplicate info must be.

Change-Id: I278a938b615296264446fe7d5b209021ec0121c0
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
TI thermal framework: rework initialization sequence

The duty cooling device is being registered in the
wrong place. We don't want to register a cooling device
every time a CPU is initialized.  Thus, this patch moves
the cooling device registration to module init instead.

Change-Id: Ib3cf55e8dde719c5736b201d9682ff515d2b1399
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>
OMAP2PLUS: remove compilation warning

without CONFIG_OMAP4_DUTY_CYCLE defined in kernel configuration
file, the compilation warning happens. The patch removes the
problem.

Change-Id: I76c549f7cae1f28d923829bbbbd6d062b142f3ea
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
Merge remote-tracking branch 'remotes/omap_zoom/p-android-omap-3.0' into acclaim