From: Sudeep Holla <sudeep.holla@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Michael Turquette <mike.turquette@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH 1/2] cpufreq: arm_big_little: check if the frequency is set correctly
Date: Mon, 13 Apr 2015 16:14:34 +0100 [thread overview]
Message-ID: <552BDD5A.8030107@arm.com> (raw)
In-Reply-To: <CAKohpomxRZkUWQUjHhbQ=8nTA-vXwuOvOFqFX9ocm6x9-DWysQ@mail.gmail.com>
On 13/04/15 11:25, Viresh Kumar wrote:
> On 13 April 2015 at 15:51, Sudeep Holla <sudeep.holla@arm.com> wrote:
>> Thanks Mike.
>>
>> Viresh, is it OK if we carry this patch until the clk framework can
>> handle this case ? I will add a *TODO* stating it's temporary change
>> and can be dropped once the clk layer handle it if that helps in any way
>> :).
>>
>> This issue is seen on TC2 when firmware is stress tested with continuous
>> DVFS requests.
>
> Sure.
>
Thanks, will repost the patches again after merge window to avoid
it getting lost during the merge window.
Regards,
Sudeep
next prev parent reply other threads:[~2015-04-13 15:14 UTC|newest]
Thread overview: 18+ 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-27 9:51 Sudeep Holla
2015-04-27 10:26 ` Viresh Kumar
2015-05-15 0:20 ` Rafael J. Wysocki
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=552BDD5A.8030107@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=mike.turquette@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.