From: Viresh Kumar <viresh.kumar@linaro.org>
To: Dirk Brandewie <dirk.brandewie@gmail.com>
Cc: Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH 0/5] Add P state driver for Intel Core Processors
Date: Thu, 14 Feb 2013 09:38:21 +0530 [thread overview]
Message-ID: <CAOh2x=nwHbbngQm1PE7SfOLbHs3oMMb74zHXD9721OJzWo1+Tg@mail.gmail.com> (raw)
In-Reply-To: <511BC16C.7040807@gmail.com>
On Wed, Feb 13, 2013 at 10:08 PM, Dirk Brandewie
<dirk.brandewie@gmail.com> wrote:
> For the case where both are built-in the load order works my driver uses
> device_initcall() and acpi_cpufreq uses late_initcall().
>
> For the case where both are a module (which I was sure I tested) you are
> right
> I will have to do something.
>
> For now I propose to make my driver built-in only while I sort out the right
> solution for the module build. Does this seem reasonable to everyone?
Of-course i am missing something here. Why would anybody want to insert
acpi-cpufreq module when the system supports the pstate driver.
In case they are mutually exclusive, then we can have something like
depends on !ACPI-DRIVER in the kconfig option of pstate driver.
next prev parent reply other threads:[~2013-02-14 4:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 17:02 [PATCH 0/5] Add P state driver for Intel Core Processors dirk.brandewie
2013-02-06 17:02 ` [PATCH 1/5] cpufreq: Retrieve current frequency from scaling drivers with internal governors dirk.brandewie
2013-02-07 13:46 ` Viresh Kumar
2013-02-06 17:02 ` [PATCH 2/5] cpufreq: Only call cpufreq_out_of_sync() for driver that implement cpufreq_driver.target() dirk.brandewie
2013-02-06 17:02 ` [PATCH 2/5] cpufreq: Only call cpufreq_out_of_sync() with drivers " dirk.brandewie
2013-02-07 10:33 ` Viresh Kumar
2013-02-06 17:02 ` [PATCH 3/5] cpufreq: Do not track governor name for scaling drivers with internal governors dirk.brandewie
2013-02-07 10:43 ` Viresh Kumar
2013-02-07 13:45 ` Viresh Kumar
2013-02-06 17:02 ` [PATCH 4/5] cpufreq_stats: do not remove sysfs files if frequency table is not present dirk.brandewie
2013-02-06 17:02 ` [PATCH 5/5] cpufreq/x86: Add P-state driver for sandy bridge dirk.brandewie
2013-02-07 14:01 ` Viresh Kumar
2013-02-07 10:42 ` [PATCH 0/5] Add P state driver for Intel Core Processors Viresh Kumar
2013-02-07 14:02 ` Viresh Kumar
2013-02-07 22:43 ` Rafael J. Wysocki
2013-02-12 21:49 ` Dave Jones
2013-02-13 16:38 ` Dirk Brandewie
2013-02-13 21:17 ` Rafael J. Wysocki
2013-02-14 18:38 ` [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate dirk.brandewie
2013-02-14 22:56 ` Yinghai Lu
2013-02-15 4:23 ` Viresh Kumar
2013-02-15 12:30 ` Rafael J. Wysocki
2013-02-15 13:28 ` Viresh Kumar
2013-02-15 16:12 ` Dirk Brandewie
2013-02-15 16:15 ` dirk.brandewie
2013-02-14 4:08 ` Viresh Kumar [this message]
2013-02-14 12:21 ` [PATCH 0/5] Add P state driver for Intel Core Processors Rafael J. Wysocki
2013-02-14 15:23 ` Dirk Brandewie
2013-02-14 15:34 ` Dirk Brandewie
2013-02-14 17:36 ` Rafael J. Wysocki
2013-02-13 20:14 ` [PATCH] cpufreq/intel_pstate: Change to disallow module build dirk.brandewie
2013-02-13 20:14 ` dirk.brandewie
2013-02-14 16:10 ` Viresh Kumar
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='CAOh2x=nwHbbngQm1PE7SfOLbHs3oMMb74zHXD9721OJzWo1+Tg@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=dirk.brandewie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).