From: Dave Gerlach <d-gerlach@ti.com>
To: <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>
Cc: <linux-pm@vger.kernel.org>, Nishanth Menon <nm@ti.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [RFC PATCH] PM / OPP: Don't support OPP if it provides supported-hw but platform does not
Date: Fri, 23 Sep 2016 15:09:28 -0500 [thread overview]
Message-ID: <57E58BF8.5050506@ti.com> (raw)
In-Reply-To: <20160923200747.3948-1-d-gerlach@ti.com>
Hi,
On 09/23/2016 03:07 PM, Dave Gerlach wrote:
> The OPP framework allows each OPP to set a opp-supported-hw property
> which provides values that are matched against supported_hw values
> provided by the platform to limit support for certain OPPs on specific
> hardware. Currently, if the platform does not set supported_hw values,
> all OPPs are interpreted as supported, even if they have provided their
> own opp-supported-hw values.
>
> If an OPP has provided opp-supported-hw, it is indicating that there is
> some specific hardware configuration it is supported by. These constraints
> should be honored, and if no supported_hw has been provided by the
> platform, there is no way to determine if that OPP is actually supported,
> so it should be marked as not supported.
>
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
> ---
Currently only the sti-cpufreq and forthcoming ti-cpufreq [1] driver are
making use of dev_pm_opp_set_supported_hw so maybe nobody has seen this
yet or the framework was designed to work as it does.
I would think that if an OPP provides a set of constraints that define
when it is supported and we can't tell if we can meet those, we should
disable an OPP rather than enable it. Otherwise, what was the point of
providing constraints?
Regards,
Dave
[1] http://www.spinics.net/lists/arm-kernel/msg527921.html
> drivers/base/power/opp/of.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/power/opp/of.c b/drivers/base/power/opp/of.c
> index 1dfd3dd92624..ccccaf9f8968 100644
> --- a/drivers/base/power/opp/of.c
> +++ b/drivers/base/power/opp/of.c
> @@ -71,8 +71,18 @@ static bool _opp_is_supported(struct device *dev, struct opp_table *opp_table,
> u32 version;
> int ret;
>
> - if (!opp_table->supported_hw)
> - return true;
> + if (!opp_table->supported_hw) {
> + /*
> + * In the case that no supported_hw has been set by the
> + * platform but there is an opp-supported-hw value set for
> + * an OPP then the OPP should not be enabled as there is
> + * no way to see if the hardware supports it.
> + */
> + if (of_find_property(np, "opp-supported-hw", NULL))
> + return false;
> + else
> + return true;
> + }
>
> while (count--) {
> ret = of_property_read_u32_index(np, "opp-supported-hw", count,
>
next prev parent reply other threads:[~2016-09-23 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 20:07 [RFC PATCH] PM / OPP: Don't support OPP if it provides supported-hw but platform does not Dave Gerlach
2016-09-23 20:09 ` Dave Gerlach [this message]
2016-09-26 5:17 ` 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=57E58BF8.5050506@ti.com \
--to=d-gerlach@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox