OMAPDSS: DISPC: gracefully disable overlay at error

Disable overlay via ovl->disable() interface, which will
properly set flags in cache and GO bits for managers.
This allows overlay user to re-enable it on next frame,
thus recovering from FIFO underflows.

Change-Id: Iafeea91196efae82e81b41c637848accd80c07d6
Signed-off-by: Sergiy Kibrik <sergiy.kibrik@globallogic.com>
Merge remote-tracking branch 'origin/p-linux-omap-3.4' into p-android-omap-3.4

* origin/p-linux-omap-3.4:
  OMAPDSS: DISPC: gracefully disable overlay at error

Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
OMAPDSS: DISPC: raise GFX priority in case of TV output

Set arbitration bit on GFX pipeline if it's associated to
TV output, as it always has real-time throughput constraints,
while GFX FIFO is much smaller then FIFOs in video pipes and
often causes underflows on high resolutions.

Change-Id: If349b02dd4c9240378c69acc58eeed62ba695479
Signed-off-by: Sergiy Kibrik <sergiy.kibrik@globallogic.com>

Conflicts:
	drivers/video/omap2/dss/dispc.c
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Revert "OMAP4:HDMI: Device can't boot with HDMI cable plugged"

This reverts commit a6444f1f83eec320820f4d36506f127db9250d02.

Clocks "dss_fck" should not be enabled directly. HDMI driver
should use pm_runtime_enable/disable to switch on/off dss clocks.
Accessing "dss_fck" causing device misbehaviour such as hangs on
boot when HDMI cable plugged in or fails during enter to suspend.

Change-Id: I27ddc61f65b0d9577016c5ae17f4eefe4e5cf8a8
Signed-off-by: Ruslan Ruslichenko <x0191366@ti.com>
ARM: OMAP44xx: Remove dss_fck clock

As dss_fck should not be used directly, so remove it from
clock data. To manage dss_fck software now should use
omap_hwmod_enable()/omap_hwmod_disable() interface which
will automatically switch on/off required clocks.

Change-Id: I5cbd19a3eec7c2eb90f03cb87167b907db28c546
Signed-off-by: Ruslan Ruslichenko <x0191366@ti.com>
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Merge remote-tracking branch 'origin/p-linux-omap-3.4' into p-android-omap-3.4

* origin/p-linux-omap-3.4:
  ARM: OMAP44xx: Remove dss_fck clock

Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
OMAPDSS: DSS: enable MFLAG support for 4470.

This patch enables MFLAG support. The underflows on DSS pipes
happens sometimes because DSS works without a high priority on L3.
Now MFLAG is enabled and when MFLAG is asserted - DSS ables to fill
DMA buffers in time without underflows because of priority on L3.

Change-Id: If6cbdab0a2afb490a6d4dbd327dc5c2b0583a274
Signed-off-by: Artem Rudenko <artemrudenko@ti.com>
OMAPDSS:CEC: Unregistration cec keyboard for hdmi suspend

Unregistration cec keyboard for hdmi suspend was added

Change-Id: I79ce9041d45bd601c72be7b9df7989cfec6bbf92
Signed-off-by: Oleksandr Krol <oleksandr.krol@globallogic.com>
OMAPDSS: HDCP: Fix compilation warning

Fix following compilation warning:
...
drivers/video/omap2/dss/hdcp_ddc.c:33: warning: 'hdcp_suspend_resume_auto_ri' defined but not used
...

Change-Id: Icbdc5d4fe85529833d7d83fb17d8c1083fdb6031
Signed-off-by: Victor Kleinik <x0150886@ti.com>
ASoC: TWL6040: ADD VAUX2 regulator for AV switch

An AV switch is used in Blaze/SDP4430 to switch headset jack pin 3
between headset microphone and video output. AV switch is then a
consumer of VAUX2 supply. The corresponding consumer-supply is added
to have VAUX2 supply when headset microphone is in use.

This is considered non-essential, so if the driver is unable to
acquire the VAUX2 supply, it will gracefully continue.

Change-Id: Ie9ff712f9ded2f1e2f7c00867818d8cb499a6fc1
Signed-off-by: Misael Lopez Cruz <misael.lopez@ti.com>
Signed-off-by: Gabriel M. Beddingfield <gabrbedd@ti.com>
Signed-off-by: Victor Kleinik <x0150886@ti.com>
staging: omapdrm: Use vmalloc on resume path

Due to memory fragmentation kmalloc sometimes can't do high-order
memory allocation (128k, order 5) on resume path and kernel crashes.
Seems omap_dmm_resume() is only place where such an allocation take
place and therefore it should be fixed.

This patch uses vmalloc instead kmalloc so that phisically
non-contiguous memory can be allocated.

Change-Id: I85569ea4d30996e89725b6984191f38a3b5545ee
Signed-off-by: Semen Protsenko <semen.protsenko@ti.com>
TI-TFW: OMAP44xx: ondie-governor: Add possibility to set platform data

This patch adds possibility to overwrite default governor settings
like thermal_zones for specific boards.

Change-Id: I3f17bb5581f3465cc687e0bc29e1ad572f644379
Signed-off-by: Ruslan Ruslichenko <x0191366@ti.com>
ARM: OMAP4: SDP/Tablet44xx: Add omap_die_governor platform data

As on most of OMAP4460/70 SOM's we have Standard DDR2 which can
operate on temperatures from -25C to +85C, so we need to overwrite
default thermal governor zones to lower temperatures, so that it
won't allow DDR to overheat.
Otherways device will crash during long workload with errors like
this:

"emif emif.1: SDRAM temperature exceeds operating limit.. Needs shut down!!!"

Change-Id: Id9d3e55617c5f6716434a19f539ea1405360e2a7
Signed-off-by: Ruslan Ruslichenko <x0191366@ti.com>
Revert "staging: omapdrm: Use vmalloc on resume path"

This reverts commit 07f188e857a086eacc7c0b1f71a3512a1c3affa0.

this patch doesnt belong to p-linux as dmm-tiler is part of
only p-android-omap-3.4

doing this way causes merge conflicts in this driver when
syncing p-linux-omap-3.4 to p-android-omap-3.4.

Hence reverting the patch

Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Merge remote-tracking branch 'origin/p-linux-omap-3.4' into p-android-omap-3.4

* origin/p-linux-omap-3.4:
  Revert "staging: omapdrm: Use vmalloc on resume path"
  ARM: OMAP4: SDP/Tablet44xx: Add omap_die_governor platform data
  TI-TFW: OMAP44xx: ondie-governor: Add possibility to set platform data
  staging: omapdrm: Use vmalloc on resume path

Conflicts:
	arch/arm/mach-omap2/board-44xx-tablet.c

Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
staging: omapdrm: Use vmalloc on resume path

Due to memory fragmentation kmalloc sometimes can't do high-order
memory allocation (128k, order 5) on resume path and kernel crashes.
Seems omap_dmm_resume() is only place where such an allocation take
place and therefore it should be fixed.

This patch uses vmalloc instead kmalloc so that phisically
non-contiguous memory can be allocated.

Change-Id: I94420bd24160e9c25269d205034cc9f9325cfa4a
Signed-off-by: Semen Protsenko <semen.protsenko@ti.com>
ARM: OMAP5: OPP_NOM update for MPU

MPU now runs at 1GHz as per upcoming Data Manual Operating Conditions
Addendum revision 0.6.

Change-Id: I5bcfd679a8acc6139edef6cb491d35a6cc3efcbe
Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: OMAP5: powerdomain_data: core powerdomain only supports upto CSWR.

Core power domain OSWR/OFF mode has been descoped. remove OFF support
from logic_power_domain so that the deepest available state will be
CSWR.

Change-Id: I94a2e7e23abeb873afa031ec58361e629fc7b2d9
Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: OMAP2+: PM: remove SoC checks for enable_off mode

enable/disable/read_offmode has arch specific checks already
so remove the SoC specific checks which are redundant.

Change-Id: I1155599425e036cbc46681106bd84ab726e6f851
Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: OMAP5: powerdomain_data: remove device OFF support

Remove device OFF mode support for OMAP5 as it has been descoped from
supported feature set.

Change-Id: Ie697af0f3ac9b7d15c6a267f7068df3fc638d549
Signed-off-by: Nishanth Menon <nm@ti.com>