The following patch: [CPUFREQ] Prevent p4-clockmod from auto-binding to the ondemand governor certainly seems like a good idea. No reason to use an inefficient governor by default. However, as a side effect, setting the transition latency to this value makes it impossible for the user to _choose_ to use ondemand even when it is the best choice for his environment. On a Celeron-M processor, ondemand is useful for reducing heat output and keeping the fan from turning on all the time, and p4_clockmod is the only module that works for such processors. Until 2.6.29 this was a very useful thing.
I guess I'm confused if the intent of this change was to disable p4_clockmod entirely for the purposes of eventually making it go away, or to merely disable it from being used by default.
can you use p4-clockmod with userspace governor still?
bug closed as there is no response from the bug reporter. please re-open it if the problem still exists in the latest upstream kernel.