linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH 2/2] cpufreq: arm_big_little: remove unused cpu-cluster.<n> clock name
Date: Mon, 30 Mar 2015 14:39:10 +0100	[thread overview]
Message-ID: <551951FE.3050105@arm.com> (raw)
In-Reply-To: <CAKohpo=EkWcp_vvfQQg5yUR67rhDTB286Fi1j=22qTzOMg=dKw@mail.gmail.com>



On 30/03/15 14:31, Viresh Kumar wrote:
> On 30 March 2015 at 17:57, Sudeep Holla <sudeep.holla@arm.com> wrote:
>> The "cpu-cluster.<n>" used to get the cluster clock is not used by any
>> platform. Moreover __of_clk_get_by_name used in clk_get return error if
>> the "clock-names" in the DT doesn't match this string. When using DT,
>> it's not compulsory to specify the clock name unless there are multiple
>> clock input entries in the consumer.
>>
>> This patch removes the unused clock string from the driver.
>>
>> Cc: Viresh Kumar <viresh.kumar@linaro.org>
>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>> ---
>>   drivers/cpufreq/arm_big_little.c | 4 +---
>>   1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/drivers/cpufreq/arm_big_little.c b/drivers/cpufreq/arm_big_little.c
>> index 3fc676c63f91..813315cd0247 100644

[...]

>> @@ -344,8 +343,7 @@ static int _get_cluster_clk_and_freq_table(struct device *cpu_dev)
>>                  goto free_opp_table;
>>          }
>>
>> -       name[12] = cluster + '0';
>> -       clk[cluster] = clk_get(cpu_dev, name);
>> +       clk[cluster] = clk_get(cpu_dev, NULL);
>>          if (!IS_ERR(clk[cluster])) {
>>                  dev_dbg(cpu_dev, "%s: clk: %p & freq table: %p, cluster: %d\n",
>>                                  __func__, clk[cluster], freq_table[cluster],
>
> What about non-DT platforms? Yeah, even I am not sure if any such
> platform will be there on not, using this driver..
>

Hope we don't have any in future :)

> But otherwise,
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>

Thanks.

  reply	other threads:[~2015-03-30 13:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 12:27 [PATCH 1/2] cpufreq: arm_big_little: check if the frequency is set correctly Sudeep Holla
2015-03-30 12:27 ` [PATCH 2/2] cpufreq: arm_big_little: remove unused cpu-cluster.<n> clock name Sudeep Holla
2015-03-30 13:31   ` Viresh Kumar
2015-03-30 13:39     ` Sudeep Holla [this message]
2015-03-30 13:27 ` [PATCH 1/2] cpufreq: arm_big_little: check if the frequency is set correctly Viresh Kumar
2015-03-30 13:39   ` Sudeep Holla
2015-03-31  1:48     ` Michael Turquette
2015-03-31  9:24       ` Sudeep Holla
2015-04-01 10:01         ` Sudeep Holla
2015-04-01 21:48         ` Michael Turquette
2015-04-02  8:55           ` Sudeep Holla
2015-04-13  5:08             ` Michael Turquette
2015-04-13 10:21               ` Sudeep Holla
2015-04-13 10:25                 ` Viresh Kumar
2015-04-13 15:14                   ` Sudeep Holla
  -- strict thread matches above, loose matches on Subject: below --
2015-04-27  9:51 Sudeep Holla
2015-04-27  9:51 ` [PATCH 2/2] cpufreq: arm_big_little: remove unused cpu-cluster.<n> clock name Sudeep Holla

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=551951FE.3050105@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-pm@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).