From: Kevin Hilman <khilman@baylibre.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
ulf.hansson@linaro.org, Nishanth Menon <nm@ti.com>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
rnayak@codeaurora.org, lina.iyer@linaro.org
Subject: Re: [PATCH V3 0/7] PM / Domains: Implement domain performance states
Date: Fri, 10 Mar 2017 12:38:19 -0800 [thread overview]
Message-ID: <m237ekrhok.fsf@baylibre.com> (raw)
In-Reply-To: <cover.1487926924.git.viresh.kumar@linaro.org> (Viresh Kumar's message of "Fri, 24 Feb 2017 14:36:32 +0530")
Viresh Kumar <viresh.kumar@linaro.org> writes:
> This series contain V3 of both the bindings and the code that implement
> them. They were sent separately earlier.
>
> Some platforms have the capability to configure the performance state of
> their power domains. The process of configuring the performance state is
> pretty much platform dependent and we may need to work with a wide range
> of configurables. For some platforms, like Qcom, it can be a positive
> integer value alone, while in other cases it can be voltage levels, etc.
Why limit it to just voltage levels.
As I suggested earlier, I think this should use OPPs. Remember that a
PM domain is not limited to a hardware power domain, but is just a
grouping mechanism for devices that share some PM properties. As
mentioned by Geert, this can also be a clock domain, where frequencies
would make sense as well. One can imagine using this type of PM domain
to manage an interconnect/bus which has scalable voltage/frequencies as
well.
Kevin
next prev parent reply other threads:[~2017-03-10 20:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 9:06 [PATCH V3 0/7] PM / Domains: Implement domain performance states Viresh Kumar
[not found] ` <cover.1487926924.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-24 9:06 ` [PATCH V3 1/7] PM / Domains: Introduce "performance-states" binding Viresh Kumar
2017-02-24 9:06 ` Viresh Kumar
[not found] ` <132e9200102bf2f1175567f0862596d098363d9e.1487926924.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-28 0:31 ` Rob Herring
2017-02-28 0:31 ` Rob Herring
2017-02-28 5:36 ` Viresh Kumar
2017-02-28 5:36 ` Viresh Kumar
2017-02-24 9:06 ` [PATCH V3 2/7] PM / OPP: Introduce "domain-performance-state" binding to OPP nodes Viresh Kumar
2017-02-24 9:06 ` Viresh Kumar
[not found] ` <ceb1bf5f696138c30b30743c24b619336d438d7c.1487926924.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-28 0:39 ` Rob Herring
2017-02-28 0:39 ` Rob Herring
2017-02-28 6:57 ` Viresh Kumar
2017-02-28 6:57 ` Viresh Kumar
2017-02-28 14:10 ` Rob Herring
2017-02-28 14:10 ` Rob Herring
[not found] ` <CAL_JsqLx6Y=JgaVtJPFwERQ_=5qwqp5EY1+B=cdfBJO55Vct4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-28 15:14 ` Ulf Hansson
2017-02-28 15:14 ` Ulf Hansson
[not found] ` <CAPDyKFo5TjTa-hTzNp5KCpozU87L22piCXaSjWMTr4xVkgP+Pg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-28 15:52 ` Rob Herring
2017-02-28 15:52 ` Rob Herring
2017-02-28 19:13 ` Geert Uytterhoeven
2017-03-01 6:14 ` Viresh Kumar
2017-03-01 8:45 ` Geert Uytterhoeven
2017-03-01 8:54 ` Viresh Kumar
2017-03-01 6:27 ` Rajendra Nayak
2017-03-01 23:13 ` Rob Herring
2017-03-02 3:30 ` Rajendra Nayak
2017-03-01 6:12 ` Viresh Kumar
2017-02-24 9:06 ` [PATCH V3 3/7] PM / QOS: Keep common notifier list for genpd constraints Viresh Kumar
2017-02-24 9:06 ` [PATCH V3 4/7] PM / QOS: Add DEV_PM_QOS_PERFORMANCE request Viresh Kumar
2017-02-24 9:06 ` [PATCH V3 5/7] PM / domain: Register for PM QOS performance notifier Viresh Kumar
2017-02-24 9:06 ` [PATCH V3 6/7] PM / Domains: Allow domain performance states to be read from DT Viresh Kumar
2017-02-24 9:06 ` [PATCH V3 7/7] PM / OPP: Add support to parse domain-performance-state Viresh Kumar
2017-03-10 20:38 ` Kevin Hilman [this message]
2017-03-13 10:39 ` [PATCH V3 0/7] PM / Domains: Implement domain performance states Viresh Kumar
2017-03-15 10:49 ` Viresh Kumar
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=m237ekrhok.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=lina.iyer@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=ulf.hansson@linaro.org \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.