From: Rob Herring <robherring2@gmail.com>
To: Kevin Hilman <khilman@deeprootsystems.com>,
Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawn.guo@linaro.org>,
linux-pm@vger.kernel.org,
Mark Langsdorf <mark.langsdorf@calxeda.com>
Subject: omap cpufreq driver in multi-platform kernels
Date: Tue, 26 Mar 2013 20:49:48 -0500 [thread overview]
Message-ID: <5152503C.2050503@gmail.com> (raw)
Kevin, Tony, Paul,
The omap cpufreq driver causes problems in multi-platform kernels
because it unconditionally registers with the cpufreq core and does not
check sufficiently that it is running on an omap platform. So on a
kernel with highbank and omap drivers booted on highbank, the
cpufreq-cpu0 driver fails to init. Any suggestions for how to fix? For
DT this could just be several of_machine_is_compatible checks, but I'm
not really sure for non-DT. Converting the driver to a platform driver
would be another option.
This will also affect other cpufreq-cpu0 users like iMX. And I'd guess
there may be other ARM cpufreq drivers that will cause the same issue.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: omap cpufreq driver in multi-platform kernels
Date: Tue, 26 Mar 2013 20:49:48 -0500 [thread overview]
Message-ID: <5152503C.2050503@gmail.com> (raw)
Kevin, Tony, Paul,
The omap cpufreq driver causes problems in multi-platform kernels
because it unconditionally registers with the cpufreq core and does not
check sufficiently that it is running on an omap platform. So on a
kernel with highbank and omap drivers booted on highbank, the
cpufreq-cpu0 driver fails to init. Any suggestions for how to fix? For
DT this could just be several of_machine_is_compatible checks, but I'm
not really sure for non-DT. Converting the driver to a platform driver
would be another option.
This will also affect other cpufreq-cpu0 users like iMX. And I'd guess
there may be other ARM cpufreq drivers that will cause the same issue.
Rob
next reply other threads:[~2013-03-27 1:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 1:49 Rob Herring [this message]
2013-03-27 1:49 ` omap cpufreq driver in multi-platform kernels Rob Herring
2013-03-27 2:23 ` Paul Walmsley
2013-03-27 2:23 ` Paul Walmsley
2013-03-27 13:32 ` Nishanth Menon
2013-03-27 13:32 ` Nishanth Menon
2013-03-27 16:38 ` Rob Herring
2013-03-27 16:38 ` Rob Herring
2013-03-27 17:02 ` Nishanth Menon
2013-03-27 17:02 ` Nishanth Menon
2013-03-27 17:53 ` Kevin Hilman
2013-03-27 17:53 ` Kevin Hilman
2013-03-27 17:56 ` Nishanth Menon
2013-03-27 17:56 ` Nishanth Menon
2013-03-30 22:21 ` Paul Walmsley
2013-03-30 22:21 ` Paul Walmsley
2013-04-01 17:20 ` Eduardo Valentin
2013-04-01 17:20 ` Eduardo Valentin
2013-04-01 19:14 ` Nishanth Menon
2013-04-01 19:14 ` Nishanth Menon
2013-04-01 19:27 ` Paul Walmsley
2013-04-01 19:27 ` Paul Walmsley
2013-04-01 19:46 ` Rob Herring
2013-04-01 19:46 ` Rob Herring
2013-04-01 21:58 ` Paul Walmsley
2013-04-01 21:58 ` Paul Walmsley
2013-03-27 17:48 ` Paul Walmsley
2013-03-27 17:48 ` Paul Walmsley
2013-03-27 18:02 ` Nishanth Menon
2013-03-27 18:02 ` Nishanth Menon
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=5152503C.2050503@gmail.com \
--to=robherring2@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.langsdorf@calxeda.com \
--cc=paul@pwsan.com \
--cc=shawn.guo@linaro.org \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.