diff options
| author | Tomeu Vizoso <tomeu.vizoso@collabora.com> | 2016-01-21 08:52:26 +0100 |
|---|---|---|
| committer | MyungJoo Ham <myungjoo.ham@samsung.com> | 2016-02-23 14:27:42 +0900 |
| commit | dbb0c7c430ddbe4299f3580baec0e2503f6f5a93 (patch) | |
| tree | f4fe9aff85ed49d7d61e66dbcbad45c61cc4ac16 /drivers/devfreq | |
| parent | 81f70ba233d5f660e1ea5fe23260ee323af5d53a (diff) | |
| download | linux-stable-dbb0c7c430ddbe4299f3580baec0e2503f6f5a93.tar.gz linux-stable-dbb0c7c430ddbe4299f3580baec0e2503f6f5a93.tar.bz2 linux-stable-dbb0c7c430ddbe4299f3580baec0e2503f6f5a93.zip | |
PM / devfreq: tegra: Set freq in rate callback
As per the documentation of the devfreq_dev_profile.target callback, set
the freq argument to the new frequency before returning.
This caused endless messages like this after recent changes in the core:
devfreq 6000c800.actmon: Couldn't update frequency transition information.
Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Reported-by: Tyler Baker <tyler.baker@linaro.org>
Tested-by: Thierry Reding <treding@nvidia.com>
Acked-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Diffstat (limited to 'drivers/devfreq')
| -rw-r--r-- | drivers/devfreq/tegra-devfreq.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/devfreq/tegra-devfreq.c b/drivers/devfreq/tegra-devfreq.c index 848b93ee930f..fe9dce0245bf 100644 --- a/drivers/devfreq/tegra-devfreq.c +++ b/drivers/devfreq/tegra-devfreq.c @@ -500,6 +500,8 @@ static int tegra_devfreq_target(struct device *dev, unsigned long *freq, clk_set_min_rate(tegra->emc_clock, rate); clk_set_rate(tegra->emc_clock, 0); + *freq = rate; + return 0; } |