From: Leonard Crestez <leonard.crestez@nxp•com>
To: "MyungJoo Ham" <myungjoo.ham@samsung•com>,
"Kyungmin Park" <kyungmin.park@samsung•com>,
"Chanwoo Choi" <cw00.choi@samsung•com>,
"Artur Świgoń" <a.swigon@partner•samsung.com>
Cc: Jacky Bai <ping.bai@nxp•com>,
Saravana Kannan <saravanak@google•com>,
linux-pm@vger•kernel.org, Viresh Kumar <viresh.kumar@linaro•org>,
Krzysztof Kozlowski <krzk@kernel•org>,
Alexandre Bailon <abailon@baylibre•com>,
Georgi Djakov <georgi.djakov@linaro•org>,
linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 0/2] PM / devfreq: Add dev_pm_qos support
Date: Tue, 20 Aug 2019 18:23:59 +0300 [thread overview]
Message-ID: <cover.1566314535.git.leonard.crestez@nxp.com> (raw)
Add dev_pm_qos notifies to devfreq core in order to support frequency
limits via the dev_pm_qos_add_request.
Unlike the rest of devfreq the dev_pm_qos frequency is measured in Khz,
this is consistent with current dev_pm_qos usage for cpufreq and
allows frequencies above 2Ghz (pm_qos expresses limits as s32).
Like with cpufreq the handling of min_freq/max_freq is moved to the dev_pm_qos
mechanism and this decreases the precision of the sysfs entries.
Signed-off-by: Leonard Crestez <leonard.crestez@nxp•com>
---
Changes since v2:
* Handle sysfs via dev_pm_qos (in separate patch)
* Add locking to {min,max}_freq_show
* Fix checkpatch issues (long lines etc)
Link to v2: https://patchwork.kernel.org/patch/11084279/
Changes since v1:
* Add doxygen comments for min_nb/max_nb
* Remove notifiers on error/cleanup paths. Keep gotos simple by relying on
dev_pm_qos_remove_notifier ignoring notifiers which were not added.
Link to v1: https://patchwork.kernel.org/patch/11078475/
Leonard Crestez (2):
PM / devfreq: Add dev_pm_qos support
PM / devfreq: Use dev_pm_qos for sysfs min/max_freq
drivers/devfreq/devfreq.c | 170 +++++++++++++++++++++++++++-----------
include/linux/devfreq.h | 14 +++-
2 files changed, 131 insertions(+), 53 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-08-20 15:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 15:23 Leonard Crestez [this message]
2019-08-20 15:24 ` [PATCH v3 1/2] PM / devfreq: Add dev_pm_qos support Leonard Crestez
2019-08-21 1:44 ` Chanwoo Choi
2019-08-21 13:00 ` Leonard Crestez
2019-08-22 10:14 ` Chanwoo Choi
2019-08-20 15:24 ` [PATCH v3 2/2] PM / devfreq: Use dev_pm_qos for sysfs min/max_freq Leonard Crestez
2019-08-21 2:04 ` Chanwoo Choi
2019-08-21 13:03 ` Leonard Crestez
2019-08-22 10:07 ` Chanwoo Choi
2019-08-22 10:58 ` Leonard Crestez
2019-08-22 11:10 ` Chanwoo Choi
2019-08-22 12:24 ` Leonard Crestez
2019-08-23 8:40 ` Chanwoo Choi
2019-08-23 11:47 ` Leonard Crestez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1566314535.git.leonard.crestez@nxp.com \
--to=leonard.crestez@nxp$(echo .)com \
--cc=a.swigon@partner$(echo .)samsung.com \
--cc=abailon@baylibre$(echo .)com \
--cc=cw00.choi@samsung$(echo .)com \
--cc=georgi.djakov@linaro$(echo .)org \
--cc=krzk@kernel$(echo .)org \
--cc=kyungmin.park@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=myungjoo.ham@samsung$(echo .)com \
--cc=ping.bai@nxp$(echo .)com \
--cc=saravanak@google$(echo .)com \
--cc=viresh.kumar@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox