omap4: hwmod_data: add clocks to ipu processor devices

The ipu processor hwmod devices (ipu_c0 & ipu_c1) are defined
primarily as pseudo-hwmod devices with only reset controls.
These share the same functional clock along with the ipu hwmod
device that is mainly used for controlling the MMU. This clock
name is added to these pseudo-hwmod devices, as it will improve
the robustness to any HW_AUTO settings performed within the
hwmod framework. There is no major effect on the clock framework
itself, as the clock enable & disable will simply be reference
counted and the functionality would be identical as before.

Change-Id: I865e9690b503e601df27aa0a55cfac45622c4259
Signed-off-by: Suman Anna <s-anna@ti.com>
omap: iommu: relax constraint value to allow CSWR

The iommu driver currently requests a latency constraint,
if configured in platform data, on the power domain it is
present in. These values are required only for OMAP4 and
beyond and is done to ensure the AMMU context is maintained
when the corresponding power domain goes to a low power state
during cpuidle path. The AMMU context is retained in CSWR, but
is lost in OSWR.

The current constraint value (10) for OMAP4+ is high and
restricts the power domain to remain in ON state as long as
the processor is active. This value is relaxed to 400 to
allow a lower power CSWR state during cpuidle path.

The context is saved and restored properly when suspending
the remote processor.

Change-Id: I89fd125f2244ae1691843c3c078aa6314a7ae8a6
Signed-off-by: Miguel Vadillo <vadillo@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
omap: mailbox: relax constraint to allow powerdomain to go to CSWR

The mailbox registers can be accessed and configured by other remote
processor initiators, and hence the driver has to be responsible for
maintaining the register context when they are active. This is
achieved by the mailbox driver by requesting a latency constraint
on the power domain that it belongs to.

The current constraint value (10) is high and restricts the power
domain to remain in ON state as long as a remote processor is
active. This value is relaxed to 400 to allow a lower power CSWR
state that can still retain the context during cpuidle path and
a remote processor is active.

The constraint is completely removed when the remote processor is
suspended. The mailbox context is saved and restored properly
when suspending the remote processor.

Change-Id: I152b57e982dc8e5739808cbbbe8bd5cc96223ffa
Signed-off-by: Miguel Vadillo <vadillo@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
OMAP4470: OPP: Enable SGX OPP-OV for Low Power OPP set

Initial 4470 Low Power OPP set was copied from 4460 OPP set.
4460 OPP set had SGX OPP-OV disabled by
commit 919cf0ce816b626f1d836d050a31463650f54526.
This commit is reverted and 4460 SGX OPP-OV is enabled.
Same should be done for 4470.

Change-Id: I7483a8669da79479303453495c0d41f959daa9ad
Signed-off-by: Taras Kondratiuk <taras@ti.com>
OMAPDSS: DSSCOMP: Fix incorrect num_ovls check

In setup manager IOCTL, the check to validate the number of overlays
is incorrect. Hence when all overlays are passed to setup manager IOCTL
with enable/disable, error was returned. Fix the same.

Change-Id: I8ec1a6dee9f074ebf83a39bdf113a97e2543cc70
Signed-off-by: Varadarajan, Charulatha <charu@ti.com>
Revert ducati 2.1.13 prerequisites: 6d2d426 and 1289289.

This reverts commits:
6d2d426 "remoteproc: omap: differentiate auto-suspend from system suspend"
1289289 "omap: ion: increase ducati memory by 2MB"

Change-Id: Ib3d14d9ca859bcc60f35734552bae41eaa874436
Signed-off-by: Roman Shaposhnikov <x0166637@ti.com>
Revert "Revert ducati 2.1.13 prerequisites: 6d2d426 and 1289289."

This reverts commit 15ff8652b93e43d0eb0a65a3f31d47b97dde6290.

Change-Id: I3a8468c8ebb22ea46aedc57bcb90a0b98f5bb5f8
Signed-off-by: Dmytro Kedrovskyi <x0169235@ti.com>
omap: rpres: add api to lookup max frequency for a remote device

A new public function, rpres_get_max_freq, is added to perform a
lookup for the maximum supported frequency from the OPP table for
a remote processor device.

This API can be used by the remote resource layer in sharing this
data to the remote processor application code for performing power
related policy decisions.

Change-Id: Idbea6884fa47b3bd1f000b6f696fbbcf7036a6ee
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Juan Gutierrez <jgutierrez@ti.com>
Signed-off-by: Paul Hunt <hunt@ti.com>
Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
rpmsg: resmgr: add support for resource-data requests from rproc

Support has been added to the remote processor resource manager layer
to allow the remote processor to query for certain data associated
with a remote resource.

A request to query the maximum frequency for IVAHD and FDIF is
currently the only supported resource-data request. This information
is to be used to help the remote processor application code make power
and performance related policy decisions for different usecases.

Change-Id: I644a7603d3e493de4d5669e8994b9809e808e8a0
Signed-off-by: Juan Gutierrez <jgutierrez@ti.com>
Signed-off-by: Paul Hunt <hunt@ti.com>
Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
gcx: changed GC_THREAD_TIMEOUT value

GC_THREAD_TIMEOUT value was changed from 1000 to 20.
This change gives us nearly 60mA power saving.

Change-Id: If5a2e3af2e1771f25c1697424151a822312e91f5
Signed-off-by: Victor Kleinik <x0150886@ti.com>
omap: increase default carveout size for DSP to 6MB

The default memory carveout size for DSP has been increased from
4MB to 6MB to accomodate adding new libraries to the DSP product
base-images.

Change-Id: I55b9e0550b93c1d41ecd2452f45b74bfc14bd9b1
Signed-off-by: Suman Anna <s-anna@ti.com>
OMAPDSS: DSSCOMP:remove compilation warnings