From: Viresh Kumar <viresh.kumar@linaro.org>
To: rjw@sisk.pl
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/2] cpufreq: fix transition_ongoing count for powernow-k8
Date: Fri, 13 Sep 2013 18:29:37 +0530 [thread overview]
Message-ID: <cover.1379062834.git.viresh.kumar@linaro.org> (raw)
This has been running in my mind since few days... That we have fixed cpufreq
core and all other drivers for transition serialization but what about
powernow-k8? It is somewhat special (even more than exynos5440).. It queues a
work from ->target() and may or maynot send notifications at all..
Finally I have got a solution now (detailed logs in the patch)..
These must go with following patchset:
https://lkml.org/lkml/2013/9/12/173
Compile tested only..
Viresh Kumar (2):
cpufreq: Create cpufreq_transition_complete()
cpufreq: powernow-k8: mark freq transition complete on error cases
drivers/cpufreq/cpufreq.c | 25 ++++++++++++-----------
drivers/cpufreq/powernow-k8.c | 47 +++++++++++++++++++++++++++++++------------
include/linux/cpufreq.h | 7 +++++++
3 files changed, 54 insertions(+), 25 deletions(-)
--
1.7.12.rc2.18.g61b472e
next reply other threads:[~2013-09-13 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 12:59 Viresh Kumar [this message]
2013-09-13 12:59 ` [PATCH 1/2] cpufreq: Create cpufreq_transition_complete() Viresh Kumar
2013-09-13 12:59 ` [PATCH 2/2] cpufreq: powernow-k8: mark freq transition complete on error cases Viresh Kumar
2013-09-13 23:42 ` [PATCH 0/2] cpufreq: fix transition_ongoing count for powernow-k8 Rafael J. Wysocki
2013-09-14 4:29 ` Viresh Kumar
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=cover.1379062834.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
/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.