aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/plat-omap/include/plat/rpres.h
Commit message (Collapse)AuthorAgeFilesLines
* omap: rpres: add api to lookup max frequency for a remote deviceJuan Gutierrez2012-08-091-0/+2
| | | | | | | | | | | | | | | | 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>
* omap: rpres: skip the creation of already created devicesMiguel Vadillo2011-07-201-0/+1
| | | | | | | | | | | | | | | | | | Some devices like: - iva - dsp - fdif are being created for pm purposes and create them again is not recommended. For these devices the pm framework is exporting api's to get them. If a resource is already created use the api to get the device and add the platform data and information needed for rpres to control such device. Change-Id: I6640883f911f4c21d204c20ded1ced104af5ed7c Signed-off-by: Miguel Vadillo <vadillo@ti.com>
* omap: rpres: adding constraints APIMiguel Vadillo2011-06-301-3/+10
| | | | | | | | | | | | | | Adding PM constraints to rpres driver: - scale_dev: request a change in the opp of the device or the domain the device is part of. - set_lat: request a latency constraint on the device or the domain the device is part of. - set_bw: set the minimum bus troughput for this device. Change-Id: I711fc5c68d2cab812c399764f429d1ada37ced2b Signed-off-by: Miguel Vadillo <vadillo@ti.com> Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
* OMAP: rpres: adding new framework rpresFernando Guzman Lugo2011-06-221-0/+49
This new module create devices for resources than can be access by the moteprocessor in omap4. Note: sl2if has follow this sequence: - sl2if * A sequence is need to request them: > iva_hd > iva_seq0 > iva_seq1 > sl2if * A sequence is need to release them: > iva_seq1 > iva_seq0 > sl2if > iva_hd * Otherwise the PM transitions behavior is abnormal Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com> Signed-off-by: Miguel Vadillo <vadillo@ti.com>