From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: Q: acpi-cpufreq module auto-loading after processor driver change
Date: Thu, 6 Jun 2013 16:09:47 -0700 [thread overview]
Message-ID: <20130606230947.GA31618@kroah.com> (raw)
In-Reply-To: <3155099.bCeEkuSrim@vostro.rjw.lan>
On Fri, Jun 07, 2013 at 12:44:44AM +0200, Rafael J. Wysocki wrote:
> So far I have verified that topology_init() is executed before acpi_init()
> (which appears to be pure coincidence, but oh well), so even the *ordering*
> is the same as before. The only difference is that the device in question
> now has a driver bound to it and it didn't before (the driver was bound to
> something else).
>
> Hmm. I suspect udev just thinks "ok, I have found a driver for that device,
> so I don't need to look for one any more" and that's why it doesn't load
> acpi_cpufreq. If that's the case, is there any way to make it load all
> matching modules anyway?
udev should call modprobe with an alias for the device which _should_
try to load all modules that match the alias. So take a look at kmod to
see if something is odd there.
sorry,
greg k-h
next prev parent reply other threads:[~2013-06-06 23:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 21:38 Q: acpi-cpufreq module auto-loading after processor driver change Rafael J. Wysocki
2013-05-30 21:54 ` Rafael J. Wysocki
2013-06-06 20:24 ` Greg Kroah-Hartman
2013-06-06 21:51 ` Rafael J. Wysocki
2013-06-06 22:13 ` Rafael J. Wysocki
2013-06-06 22:21 ` Greg Kroah-Hartman
2013-06-06 22:44 ` Rafael J. Wysocki
2013-06-06 23:09 ` Greg Kroah-Hartman [this message]
2013-06-07 1:01 ` Rafael J. Wysocki
2013-06-07 2:08 ` [PATCH] ACPI / cpufreq: Add ACPI processor device IDs to acpi-cpufreq Rafael J. Wysocki
2013-06-07 3:33 ` 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=20130606230947.GA31618@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@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