[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190214013042.254790-1-mka@chromium.org>
Date: Wed, 13 Feb 2019 17:30:38 -0800
From: Matthias Kaehlcke <mka@...omium.org>
To: MyungJoo Ham <myungjoo.ham@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-tegra@...r.kernel.org,
Lukasz Luba <l.luba@...tner.samsung.com>
Cc: Matthias Kaehlcke <mka@...omium.org>
Subject: [PATCH 0/4] PM / devfreq: Refactor load monitoring
The devfreq core currently expects governors to call specific load
monitor functions on certain DEVFREQ_GOV_ events. Since the devfreq
core itself invokes the event handler it can as well call the
corresponding load monitor functions itself. This series refactors
the code to do this for DEVFREQ_GOV_START/STOP/SUSPEND and RESUME.
In the process it also moves some repeated code involved in starting
and stopping the governor into helper functions.
Unfortunately I could only do limited testing of this series with a 4.19
kernel and few rather inactive devfreq devices. In this sense additional
testing would be appreciated.
Thanks
Matthias
Matthias Kaehlcke (4):
PM / devfreq: Track overall load monitor state instead of
'stop_polling'
PM / devfreq: Handle monitor suspend/resume in the devfreq core
PM / devfreq: Add devfreq_governor_start/stop()
PM / devfreq: Handle monitor start/stop in the devfreq core
drivers/devfreq/devfreq.c | 185 +++++++++++++---------
drivers/devfreq/governor.h | 4 -
drivers/devfreq/governor_simpleondemand.c | 16 --
drivers/devfreq/tegra-devfreq.c | 4 -
include/linux/devfreq.h | 4 +-
5 files changed, 111 insertions(+), 102 deletions(-)
--
2.20.1.791.gb4d0f1c61a-goog
Powered by blists - more mailing lists