From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, robin.randhawa@arm.com,
Steve.Bannister@arm.com, Liviu.Dudau@arm.com,
charles.garcia-tobin@arm.com, arvind.chauhan@arm.com,
dave.martin@arm.com
Subject: Re: [PATCH 00/13] CPUFreq: Fix {PRE|POST}CHANGE notification sequence
Date: Mon, 24 Jun 2013 13:58:43 +0200 [thread overview]
Message-ID: <19900521.4upM9YL2PZ@vostro.rjw.lan> (raw)
In-Reply-To: <cover.1371630975.git.viresh.kumar@linaro.org>
On Wednesday, June 19, 2013 02:22:54 PM Viresh Kumar wrote:
> PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
> should be called or both shouldn't be.
>
> In case we have started PRECHANGE notifier and found an error, we must call
> POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
> calling notifiers is complete.
>
> This isn't obeyed by many of the drivers and core wasn't forcing it.
>
> This patchset first fixes all the driver to follow it strictly and then adds
> some protection against this. Now, we keep track of the last transaction and see
> if something went wrong.
>
> Last patch is intentionally kept towards the end, so that git bisect still works
> well for all the faulty drivers.
>
> This is pushed here and a pull request for 3.11 would be sent after few days.
>
> git://git.linaro.org/people/vireshk/linux.git cpufreq-fix-notification
>
> Viresh Kumar (13):
> cpufreq: acpi: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: arm-big-little: call CPUFREQ_POSTCHANGE notfier in error
> cases
> cpufreq: davinci: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: dbx500: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: e_powersave: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: exynos: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: imx6q: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: omap: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: pcc: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: powernow-k8: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: s3c64xx: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: tegra: call CPUFREQ_POSTCHANGE notfier in error cases
> cpufreq: make sure frequency transitions are serialized
Patches [1,5,9-10/13] applied to bleeding-edge, the ARM ones I'm expecting
to get from you and [13/13] can wait.
Thanks,
Rafael
prev parent reply other threads:[~2013-06-24 11:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 8:52 Viresh Kumar
2013-06-19 8:52 ` [PATCH 01/13] cpufreq: acpi: call CPUFREQ_POSTCHANGE notfier in error cases Viresh Kumar
2013-06-19 8:52 ` [PATCH 02/13] cpufreq: arm-big-little: " Viresh Kumar
2013-06-19 8:52 ` [PATCH 03/13] cpufreq: davinci: " Viresh Kumar
2013-06-19 8:58 ` Sekhar Nori
2013-06-19 8:52 ` [PATCH 04/13] cpufreq: dbx500: " Viresh Kumar
2013-06-19 19:42 ` Linus Walleij
2013-06-19 8:52 ` [PATCH 05/13] cpufreq: e_powersave: " Viresh Kumar
2013-06-19 12:22 ` Simon Horman
2013-06-19 14:54 ` Viresh Kumar
2013-06-19 15:08 ` Dave Jones
2013-06-19 8:53 ` [PATCH 06/13] cpufreq: exynos: " Viresh Kumar
2013-06-19 8:53 ` [PATCH 07/13] cpufreq: imx6q: " Viresh Kumar
2013-06-20 2:52 ` Shawn Guo
2013-06-19 8:53 ` [PATCH 08/13] cpufreq: omap: " Viresh Kumar
2013-06-19 14:44 ` Santosh Shilimkar
2013-06-19 8:53 ` [PATCH 09/13] cpufreq: pcc: " Viresh Kumar
2013-06-19 8:53 ` [PATCH 10/13] cpufreq: powernow-k8: " Viresh Kumar
2013-06-19 8:53 ` [PATCH 11/13] cpufreq: s3c64xx: " Viresh Kumar
2013-06-19 8:53 ` [PATCH 12/13] cpufreq: tegra: " Viresh Kumar
2013-06-19 17:11 ` Stephen Warren
2013-06-19 8:53 ` [PATCH 13/13] cpufreq: make sure frequency transitions are serialized Viresh Kumar
2013-06-24 11:43 ` Rafael J. Wysocki
2013-06-24 13:08 ` Viresh Kumar
2013-06-24 13:23 ` Rafael J. Wysocki
2013-06-24 13:16 ` Viresh Kumar
2013-06-24 13:33 ` Rafael J. Wysocki
2013-06-24 13:31 ` Viresh Kumar
2013-06-26 21:57 ` Rafael J. Wysocki
2013-06-27 4:56 ` Viresh Kumar
2013-06-27 12:15 ` Rafael J. Wysocki
2013-06-24 11:58 ` Rafael J. Wysocki [this message]
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=19900521.4upM9YL2PZ@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arvind.chauhan@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=dave.martin@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=robin.randhawa@arm.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®