cpufreq_debug_printk will print messages if

a) debugging for the specified part is activated (add
        1 for core,
        2 for drivers,
        4 for governors
   and pass value as
        cpufreq.debug=<value>
   on the kernel command line).

b) and either
        b1) printk_ratelimit() allows it to be printed,
        b2) the user disables ratelimit'ing by passing
                cpufreq.debug_ratelimit=0
            on the kernel command line, _or_
        b3) during driver initialization [unless a different
            driver has been initialized successfully] and
            unloading, and whenever a new policy is set.

            The last point may cause for numerous messages
            if an userspace-based dynamic governor is used
            which mis-uses the policy interface to set specific
            frequencies. Oh, the ACPI processor.c interface
            to the file "performance" uses the same trick,
            but that interface is marked deprecated as well,
            so I don't care. And debugging isn't activated
            normally, you know...
Signed-off-by: Dominik Brodowski <linux@brodo.de>
Signed-off-by: Dave Jones <davej@redhat.com>