summaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq/Kconfig.powerpc
diff options
context:
space:
mode:
authorPaul Gortmaker <paul.gortmaker@windriver.com>2013-01-11 13:43:45 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-01-26 00:39:12 +0100
commit43720bd6014327ac454434496cb953edcdb9f8d6 (patch)
treebe134a588abb3164b7c5f9093707e536f9c54a05 /drivers/cpufreq/Kconfig.powerpc
parented1ac6e91a3ff7c561008ba57747cd6cbc49385e (diff)
downloadlinux-43720bd6014327ac454434496cb953edcdb9f8d6.tar.gz
linux-43720bd6014327ac454434496cb953edcdb9f8d6.tar.bz2
linux-43720bd6014327ac454434496cb953edcdb9f8d6.zip
PM / tracing: remove deprecated power trace API
The text in Documentation said it would be removed in 2.6.41; the text in the Kconfig said removal in the 3.1 release. Either way you look at it, we are well past both, so push it off a cliff. Note that the POWER_CSTATE and the POWER_PSTATE are part of the legacy tracing API. Remove all tracepoints which use these flags. As can be seen from context, most already have a trace entry via trace_cpu_idle anyways. Also, the cpufreq/cpufreq.c PSTATE one is actually unpaired, as compared to the CSTATE ones which all have a clear start/stop. As part of this, the trace_power_frequency also becomes orphaned, so it too is deleted. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Acked-by: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/Kconfig.powerpc')
0 files changed, 0 insertions, 0 deletions