From: Saravana Kannan <saravanak@google.com>
To: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Saravana Kannan <saravanak@google.com>,
kernel-team@android.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/3] Add required-opps support to devfreq passive gov
Date: Fri, 21 Jun 2019 17:34:45 -0700 [thread overview]
Message-ID: <20190622003449.33707-1-saravanak@google.com> (raw)
The devfreq passive governor scales the frequency of a "child" device
based on the current frequency of a "parent" device (not parent/child in
the sense of device hierarchy). As of today, the passive governor
requires one of the following to work correctly:
1. The parent and child device have the same number of frequencies
2. The child device driver passes a mapping function to translate from
parent frequency to child frequency.
When (1) is not true, (2) is the only option right now. But often times,
all that is required is a simple mapping from parent's frequency to
child's frequency.
Since OPPs already support pointing to other "required-opps", add
support for using that to map from parent device frequency to child
device frequency. That way, every child device driver doesn't have to
implement a separate mapping function anytime (1) isn't true.
-Saravana
Saravana Kannan (3):
OPP: Allow required-opps even if the device doesn't have power-domains
OPP: Add function to look up required OPP's for a given OPP
PM / devfreq: Add required OPPs support to passive governor
drivers/devfreq/governor_passive.c | 25 +++++++++++--
drivers/opp/core.c | 56 +++++++++++++++++++++++++++++-
drivers/opp/of.c | 14 --------
include/linux/pm_opp.h | 11 ++++++
4 files changed, 89 insertions(+), 17 deletions(-)
--
2.22.0.410.gd8fdbe21b5-goog
next reply other threads:[~2019-06-22 0:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 0:34 Saravana Kannan [this message]
2019-06-22 0:34 ` [PATCH v1 1/3] OPP: Allow required-opps even if the device doesn't have power-domains Saravana Kannan
2019-06-22 0:34 ` [PATCH v1 2/3] OPP: Add function to look up required OPP's for a given OPP Saravana Kannan
2019-06-22 11:49 ` Chanwoo Choi
2019-06-22 21:41 ` Saravana Kannan
2019-06-23 4:27 ` Chanwoo Choi
2019-06-23 6:07 ` Saravana Kannan
2019-06-22 0:34 ` [PATCH v1 3/3] PM / devfreq: Add required OPPs support to passive governor Saravana Kannan
2019-06-22 12:00 ` Chanwoo Choi
2019-06-22 21:45 ` Saravana Kannan
2019-06-24 9:43 ` [PATCH v1 0/3] Add required-opps support to devfreq passive gov Viresh Kumar
2019-06-24 22:17 ` Saravana Kannan
2019-06-25 4:10 ` Viresh Kumar
2019-06-25 5:00 ` Saravana Kannan
2019-06-25 5:22 ` Viresh Kumar
2019-06-25 5:29 ` Saravana Kannan
2019-06-26 6:32 ` Viresh Kumar
2019-06-26 18:10 ` Saravana Kannan
2019-06-28 6:49 ` Viresh Kumar
2019-06-28 20:26 ` Saravana Kannan
2019-07-11 23:16 ` Saravana Kannan
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=20190622003449.33707-1-saravanak@google.com \
--to=saravanak@google.com \
--cc=cw00.choi@samsung.com \
--cc=kernel-team@android.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=vireshk@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).