On Wed, Sep 25, 2013 at 10:40 PM, Viresh Kumar wrote:
> On 26 September 2013 10:47, Yinghai Lu wrote:
>> can you put this one in acpi tree?
>
> Its already applied in Rafael's linux-next branch.. Do you want something
> else?
sorry, I missed that.
I still had that in local patches directory, bu
On 26 September 2013 10:47, Yinghai Lu wrote:
> can you put this one in acpi tree?
Its already applied in Rafael's linux-next branch.. Do you want something
else?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Fri, Sep 20, 2013 at 10:43 AM, Yinghai Lu wrote:
> If the hw support intel_pstate and acpi_cpufreq, intel_pstate will
> get loaded first.
>
> acpi_cpufreq_init will call acpi_cpufreq_early_init()
> and that will allocate perf data and init those perf data in ACPI core,
> (that will cover all cp
On Fri, Sep 20, 2013 at 10:43 AM, Yinghai Lu wrote:
> If the hw support intel_pstate and acpi_cpufreq, intel_pstate will
> get loaded first.
>
> acpi_cpufreq_init will call acpi_cpufreq_early_init()
> and that will allocate perf data and init those perf data in ACPI core,
> (that will cover all cp
If the hw support intel_pstate and acpi_cpufreq, intel_pstate will
get loaded first.
acpi_cpufreq_init will call acpi_cpufreq_early_init()
and that will allocate perf data and init those perf data in ACPI core,
(that will cover all cpus). But later it will free them as
cpufreq_register_driver(acpi
5 matches
Mail list logo
