linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	Linux ACPI <linux-acpi@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: skip loading acpi_cpufreq after intel_pstate
Date: Fri, 20 Sep 2013 10:08:07 -0700	[thread overview]
Message-ID: <CAE9FiQUXGtNeAS70Mr6Nscax26dRoXTCyb28gz1iX2j1s8Nojw@mail.gmail.com> (raw)
In-Reply-To: <CAKohpokdyk9hfBreVeXttN23biTVjWiJRm8eYkfAjLz+cbnreQ@mail.gmail.com>

On Thu, Sep 19, 2013 at 11:10 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 20 September 2013 10:56, Yinghai Lu <yinghai@kernel.org> wrote:
>> If the hw support intel_pstate and acpi_cpufreq, intel_pstate will
>> get loaded at first.
>
> s/at //
>
>>
>> acpi_cpufreq_init will call acpi_cpufreq_early_init()
>> and it allocate perf data and init those perf data in ACPI core, (that
>
> s/it /that will /
>
>> will go over all cpus).
>
> s/go over/cover/
>
>> but late it will free them as cpufreq_register_driver(acpi_cpufreq) will
>
> s/late/later
>
>> return fail as init_pstate already take over before.
>
> write it as: fail as intel_pstate is already registered.
>
>> Use cpufreq_get_current_driver() to check if we can skip the
>> acpi_cpufreq loading.
>
> The below material looks to be a separate issue and so we
> probably break this patch into two?

ok, check that.

Thanks

Yinghai

      reply	other threads:[~2013-09-20 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20  5:26 [PATCH] cpufreq: skip loading acpi_cpufreq after intel_pstate Yinghai Lu
2013-09-20  6:10 ` Viresh Kumar
2013-09-20 17:08   ` Yinghai Lu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAE9FiQUXGtNeAS70Mr6Nscax26dRoXTCyb28gz1iX2j1s8Nojw@mail.gmail.com \
    --to=yinghai@kernel.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).