From: Saravana Kannan <skannan@codeaurora.org>
To: Saravana Kannan <skannan@codeaurora.org>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PM / devfreq: Use freq_table for available_frequencies
Date: Mon, 14 Apr 2014 13:51:37 -0700 [thread overview]
Message-ID: <534C4A59.8040507@codeaurora.org> (raw)
In-Reply-To: <1397184881-12223-1-git-send-email-skannan@codeaurora.org>
MyungJoo/Kyungmin,
Bump. Can we accept this patch please?
-Saravana
On 04/10/2014 07:54 PM, Saravana Kannan wrote:
> Some devices use freq_table instead of OPP. For those devices, the
> available_frequencies file shows up empty. Fix that by using freq_table to
> generate the available_frequencies data when OPP is not present.
>
> Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
> ---
> drivers/devfreq/devfreq.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
> index 2042ec3..a715d15 100644
> --- a/drivers/devfreq/devfreq.c
> +++ b/drivers/devfreq/devfreq.c
> @@ -912,19 +912,26 @@ static ssize_t available_frequencies_show(struct device *d,
> struct devfreq *df = to_devfreq(d);
> struct device *dev = df->dev.parent;
> struct dev_pm_opp *opp;
> + unsigned int i = 0, max_state = df->profile->max_state;
> + bool use_opp;
> ssize_t count = 0;
> unsigned long freq = 0;
>
> rcu_read_lock();
> + use_opp = dev_pm_opp_get_opp_count(dev) > 0;
> do {
> - opp = dev_pm_opp_find_freq_ceil(dev, &freq);
> - if (IS_ERR(opp))
> - break;
> + if (use_opp) {
> + opp = dev_pm_opp_find_freq_ceil(dev, &freq);
> + if (IS_ERR(opp))
> + break;
> + } else {
> + freq = df->profile->freq_table[i++];
> + }
>
> count += scnprintf(&buf[count], (PAGE_SIZE - count - 2),
> "%lu ", freq);
> freq++;
> - } while (1);
> + } while (use_opp || (!use_opp && i < max_state));
> rcu_read_unlock();
>
> /* Truncate the trailing space */
>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-04-14 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 2:54 [PATCH] PM / devfreq: Use freq_table for available_frequencies Saravana Kannan
2014-04-14 20:51 ` Saravana Kannan [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-15 1:36 함명주
2014-04-15 5:16 ` Saravana Kannan
2014-04-15 6:30 함명주
2014-04-15 18:41 ` Saravana Kannan
2014-04-17 0:12 ` 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=534C4A59.8040507@codeaurora.org \
--to=skannan@codeaurora.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/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).