From: Gautham R Shenoy <ego@linux.vnet.ibm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@rjwysocki.net, linaro-kernel@lists.linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, srivatsa.bhat@linux.vnet.ibm.com,
ego@linux.vnet.ibm.com, svaidy@linux.vnet.ibm.com,
preeti@linux.vnet.ibm.com
Subject: Re: [PATCH] cpufreq: don't print value of .driver_data from core
Date: Thu, 27 Mar 2014 16:18:42 +0530 [thread overview]
Message-ID: <20140327104842.GB27777@in.ibm.com> (raw)
In-Reply-To: <2490cd0aaeaaeb88131c8089d491c485f08da5da.1395914766.git.viresh.kumar@linaro.org>
On Thu, Mar 27, 2014 at 03:37:22PM +0530, Viresh Kumar wrote:
> CPUFreq core doesn't control value of .driver_data and this field is completely
> driver specific. This can contain any value and not only indexes. For most of
> the drivers, which aren't using this field, its value is zero. So, printing this
> from core doesn't make any sense. Don't print it.
So after this patch, driver_data is only going to be used by drivers
which want an "unsigned int" value to be saved along with the
frequency in the frequency_table and for those who want to overload
its interpretation to indicate BOOST.
>From the core's stand point, it is useful only for determining whether
a frequency is BOOST frequency or not.
So, wouldn't it be logical to allow drivers maintain their own driver
data since the core is anyway not interested in it, and change this
.driver_data to "flags" or some such which can indicate boost ?
--
Thanks and Regards
gautham.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> drivers/cpufreq/freq_table.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/cpufreq/freq_table.c b/drivers/cpufreq/freq_table.c
> index 8e54f97..f002272 100644
> --- a/drivers/cpufreq/freq_table.c
> +++ b/drivers/cpufreq/freq_table.c
> @@ -36,8 +36,7 @@ int cpufreq_frequency_table_cpuinfo(struct cpufreq_policy *policy,
> && table[i].driver_data == CPUFREQ_BOOST_FREQ)
> continue;
>
> - pr_debug("table entry %u: %u kHz, %u driver_data\n",
> - i, freq, table[i].driver_data);
> + pr_debug("table entry %u: %u kHz\n", i, freq);
> if (freq < min_freq)
> min_freq = freq;
> if (freq > max_freq)
> @@ -175,8 +174,8 @@ int cpufreq_frequency_table_target(struct cpufreq_policy *policy,
> } else
> *index = optimal.driver_data;
>
> - pr_debug("target is %u (%u kHz, %u)\n", *index, table[*index].frequency,
> - table[*index].driver_data);
> + pr_debug("target index is %u, freq is:%u kHz\n", *index,
> + table[*index].frequency);
>
> return 0;
> }
> --
> 1.7.12.rc2.18.g61b472e
>
next prev parent reply other threads:[~2014-03-27 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 10:07 Viresh Kumar
2014-03-27 10:19 ` Srivatsa S. Bhat
2014-03-27 10:48 ` Gautham R Shenoy [this message]
2014-03-27 10:59 ` Viresh Kumar
2014-03-27 11:26 ` Gautham R Shenoy
2014-03-28 8:00 ` Lukasz Majewski
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=20140327104842.GB27777@in.ibm.com \
--to=ego@linux.vnet.ibm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=svaidy@linux.vnet.ibm.com \
--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
all inboxes | Powered by JetHome®