From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: spurious bL cpufreq driver messages
Date: Fri, 17 May 2013 14:36:28 -0500 [thread overview]
Message-ID: <519686BC.3090101@gmail.com> (raw)
The bL cpufreq driver appears to collide with the cpufreq-cpu0 driver.
There doesn't appear to be a functional problem, but just spurious
prints which indicate it is trying to do something. I think it needs
better checking whether the chip is actually multi-cluster. This is what
I get when I hotplug cpus:
[ 909.372319] CPU1: Booted secondary processor
[ 909.372616] cpu cpu1: get_cluster_clk_and_freq_table: init_opp_table
failed, cpu: 1, err: -61
[ 909.385411] cpu cpu1: get_cluster_clk_and_freq_table: Failed to get
data for cluster: 9
[ 909.394161] CPU2: shutdown
[ 909.400957] CPU2: Booted secondary processor
[ 909.401253] cpu cpu2: get_cluster_clk_and_freq_table: init_opp_table
failed, cpu: 2, err: -61
[ 909.414044] cpu cpu2: get_cluster_clk_and_freq_table: Failed to get
data for cluster: 9
Rob
next reply other threads:[~2013-05-17 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 19:36 Rob Herring [this message]
2013-05-18 2:03 ` spurious bL cpufreq driver messages Viresh Kumar
2013-05-18 19:51 ` Rob Herring
2013-05-20 4:36 ` Viresh Kumar
2013-05-21 16:42 ` Rob Herring
2013-05-21 23:45 ` Rafael J. Wysocki
2013-05-22 1:14 ` Viresh Kumar
2013-05-22 10:54 ` Rafael J. Wysocki
2013-05-22 10:52 ` 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=519686BC.3090101@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).