linux-stable.git/include/linux/pm_opp.h, branch v4.6.4

PM / OPP: Add dev_pm_opp_set_rate()

2016-02-10T00:11:54+00:00

This adds a routine, dev_pm_opp_set_rate(), responsible for configuring
power-supply and clock source for an OPP.

The OPP is found by matching against the target_freq passed to the
routine. This shall replace similar code present in most of the OPP
users and help simplify them a lot.

Signed-off-by: Viresh Kumar 
Reviewed-by: Stephen Boyd 
Signed-off-by: Rafael J. Wysocki

PM / OPP: Introduce dev_pm_opp_get_max_transition_latency()

2016-02-10T00:11:53+00:00

In few use cases (like: cpufreq), it is desired to get the maximum
latency for changing OPPs. Add support for that.

Signed-off-by: Viresh Kumar 
Reviewed-by: Stephen Boyd 
Signed-off-by: Rafael J. Wysocki

PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()

2016-02-10T00:11:53+00:00

In few use cases (like: cpufreq), it is desired to get the maximum
voltage latency for changing OPPs. Add support for that.

Signed-off-by: Viresh Kumar 
Reviewed-by: Stephen Boyd 
Signed-off-by: Rafael J. Wysocki

PM / OPP: get/put regulators from OPP core

2016-02-10T00:11:53+00:00

This allows the OPP core to request/free the regulator resource,
attached to a device OPP. The regulator device is fetched using the name
provided by the driver, while calling: dev_pm_opp_set_regulator().

This will work for both OPP-v1 and v2 bindings.

This is a preliminary step for moving the OPP switching logic into the
OPP core.

Signed-off-by: Viresh Kumar 
Reviewed-by: Stephen Boyd 
Signed-off-by: Rafael J. Wysocki

PM / OPP: Parse 'opp--' bindings

2015-12-10T22:08:51+00:00

OPP bindings (for few properties) allow a platform to choose a
value/range among a set of available options. The options are present as
opp--, where the platform needs to supply the  string.

The OPP properties which allow such an option are: opp-microvolt and
opp-microamp.

Add support to the OPP-core to parse these bindings, by introducing
dev_pm_opp_{set|put}_prop_name() APIs.

Signed-off-by: Viresh Kumar 
Tested-by: Lee Jones 
Signed-off-by: Rafael J. Wysocki

PM / OPP: Parse 'opp-supported-hw' binding

2015-12-10T22:08:51+00:00

OPP bindings allow a platform to enable OPPs based on the version of the
hardware they are used for.

Add support to the OPP-core to parse these bindings, by introducing
dev_pm_opp_{set|put}_supported_hw() APIs.

Signed-off-by: Viresh Kumar 
Tested-by: Lee Jones 
Signed-off-by: Rafael J. Wysocki

PM / OPP: Prefix exported opp routines with dev_pm_opp_

2015-09-15T00:03:16+00:00

That's the naming convention followed in most of opp core, but few
routines didn't follow this, fix them.

Reviewed-by: Stephen Boyd 
Signed-off-by: Viresh Kumar 
Acked-by: Shawn Guo 
Signed-off-by: Rafael J. Wysocki

PM / OPP: Rename opp init/free table routines

2015-09-15T00:03:15+00:00

free-table routines are opposite of init-table ones, and must be named
to make that clear. Opposite of 'init' is 'exit', but those doesn't suit
really well.

Replace 'init' with 'add' and 'free' with 'remove'.

Reported-by: Pavel Machek 
Reviewed-by: Stephen Boyd 
Signed-off-by: Viresh Kumar 
Acked-by: Shawn Guo 
Signed-off-by: Rafael J. Wysocki

PM / OPP: add dev_pm_opp_get_suspend_opp() helper

2015-09-09T00:20:39+00:00

Add dev_pm_opp_get_suspend_opp() helper to obtain suspend opp.

Acked-by: Viresh Kumar 
Signed-off-by: Bartlomiej Zolnierkiewicz 
Signed-off-by: Rafael J. Wysocki

PM / OPP: add dev_pm_opp_is_turbo() helper

2015-08-07T01:17:06+00:00

Add dev_pm_opp_is_turbo() helper to verify if an opp is to be used only
for turbo mode or not.

Reviewed-by: Stephen Boyd 
Signed-off-by: Bartlomiej Zolnierkiewicz 
Signed-off-by: Viresh Kumar 
Signed-off-by: Rafael J. Wysocki