omap: remoteproc: choose ducati firmware as per platform

Ducati firmwares are different for default 1GB configuration
and 512MB system configuration. remoteproc will load
appropriate firmware as per system configuration

Change-Id: Ib790abc162c258fb8062b527b1e01c67271b199f
Signed-off-by: Devaraj Rangasamy <dev@ti.com>
OMAP4: DPLL cascading: SR: handle SRCLKLENGTH

In DPLL cascading mode SYS_CLK is gated.  This impacts many IP, including
the SmartReflex AVS modules.  To compensate for loss of SYS_CLK the
SR_xxx_SYSCLK clocks derived from the PRM use the 32K timer as a clock
source.  As such the SRCLKLENGTH value needs to be updated for this
change in frequency.  In DPLL cascading the rate of this clock should be
12.288MHz.

This patch implements three distinct changes:

1) add a 12.288MHz option to the existing sr_set_clk_length function
and give it the ability to detect whether we are in DPLL cascading
mode or not.
2) Remove optimizations in sr_configure_errgen and sr_configure_minmax to
skip sr_set_clk_length re-calibration if the clk_length parameter exists.
The assumption was that this value would never change after initial
calibration at boot; that assumption fails in light of DPLL cascading
scenario.

[Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>:
Ported and adapted to p-android-omap-3.0]

Change-Id: Ie657459e53838067139a4dd7316a6adc1f5e7259
Signed-off-by: Mike Turquette <mturquette@ti.com>
Signed-off-by: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
OMAP4: DPLL cascading: Clock: new DPLL_CORE set_rate, and M2 fixes

omap4_dpll_dpll_set_rate checks for target rate matching the clk_bypass rate
and enters Low Power Bypass in that case. Otherwise it rounds the rate and
locks the DPLL at the new rate.  Same function handles EMIF programming.

omap4_dpll_core_m2_set_rate now has better documentation, follows the same
coding style as the above function and is a bit safer by forcing clk_enable
and clk_disable calls on emif1_fck and emif2_fck.

[Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>:
Ported and adapted to p-android-omap-3.0]

Change-Id: I921be9d20fe9e9c5b5604dceb4e5aa037a6b7009
Signed-off-by: Mike Turquette <mturquette@ti.com>
Signed-off-by: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
omap: remove unused omaplfb platform device

Change-Id: Ic7d8aa22868c0cf2396ae499a1a320903e9feb31
Signed-off-by: Tony Lofthouse <a0741364@ti.com>
OMAP4: DPLL cascading: introduce devise scale function for GPU

GPU driver should be able to manage DPLL cascading constraint.
Right now sources of GPU driver are not in the kernel mainline.
So, patch introduces simple wrapper function for omap_device_scale(),
which holds DPLL cascading blocker when GPU scales to OPP higher, than
OPP50

Change-Id: I3f83b8b1c49118625f550aea031e86546ceb97fc
Signed-off-by: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
OMAP4: DPLL cascading: Fix GPU constraint

DPLL cascading constraint from GPU should be released
only when GPU is at OPP50.

Change-Id: Ice7d8e387b61737a085df4b221c6d57dcbb3813a
Signed-off-by: Taras Kondratiuk <taras@ti.com>