From: Viresh Kumar <viresh.kumar@linaro.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: "Viresh Kumar" <vireshk@kernel.org>, "nm@ti.com" <nm@ti.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
함명주 <myungjoo.ham@samsung.com>
Subject: Re: OPP: how to get the all frequency list?
Date: Tue, 29 Aug 2017 12:08:26 +0200 [thread overview]
Message-ID: <20170829100826.GD3101@ubuntu> (raw)
In-Reply-To: <599A9F8D.6080508@samsung.com>
On 21-08-17, 17:53, Chanwoo Choi wrote:
> Dear all,
>
> I have a question that how to get the all frequency list
> by using the OPP interface. (It doesn't matter whether frequency is available or not.)
>
> OPP has following three functions in order to find the proper frequency.
> - dev_pm_opp_find_freq_exact(struct device *dev, unsigned long freq, bool available);
> - dev_pm_opp_find_freq_floor(struct device *dev, unsigned long freq);
> : Search for a rounded floor freq (if opp->available is true)
> - dev_pm_opp_find_freq_ceil(struct device *dev, unsigned long freq);
> : Search for a rounded ceil freq if (opp->available is true)
>
> In this case,
> when the device using OPP tries to find the all frequencies,
> the device can't find them. The device can just find the available frequencies.
>
> If the some frequency of the device might be disabled by dev_pm_opp_disable()
> and also the device doesn't know the correct frequency value,
> the device cannot find the all frequencies by using the dev_pm_opp_find_freq_floor/ceil()
>
> It is just able to find the available frequencies if opp->available is true.
You can add the 'available' argument to the other APIs as well, just that you
need to justify them with proper examples.
--
viresh
prev parent reply other threads:[~2017-08-29 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170821085332epcas2p2e06a9d81a79ab5e71804db41bf349833@epcas2p2.samsung.com>
2017-08-21 8:53 ` OPP: how to get the all frequency list? Chanwoo Choi
2017-08-29 10:08 ` Viresh Kumar [this message]
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=20170829100826.GD3101@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=sboyd@codeaurora.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).