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 -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
