Mark the stats start time stamp when actual load monitoring is
started for accuracy.

Signed-off-by: Rajagopal Venkat <rajagopal.ven...@linaro.org>
---
 drivers/devfreq/devfreq.c |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 5782c9b..2843a22 100644
--- a/drivers/devfreq/devfreq.c
+++ b/drivers/devfreq/devfreq.c
@@ -254,9 +254,12 @@ static void devfreq_monitor(struct work_struct *work)
 void devfreq_monitor_start(struct devfreq *devfreq)
 {
        INIT_DEFERRABLE_WORK(&devfreq->work, devfreq_monitor);
-       if (devfreq->profile->polling_ms)
+       if (devfreq->profile->polling_ms) {
                queue_delayed_work(devfreq_wq, &devfreq->work,
                        msecs_to_jiffies(devfreq->profile->polling_ms));
+
+               devfreq->last_stat_updated = jiffies;
+       }
 }
 EXPORT_SYMBOL(devfreq_monitor_start);
 
@@ -498,7 +501,6 @@ struct devfreq *devfreq_add_device(struct device *dev,
        devfreq->time_in_state = devm_kzalloc(dev, sizeof(unsigned int) *
                                                devfreq->profile->max_state,
                                                GFP_KERNEL);
-       devfreq->last_stat_updated = jiffies;
        devfreq_set_freq_limits(devfreq);
 
        dev_set_name(&devfreq->dev, dev_name(dev));
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to