From: Ben Gamari <bgamari.foss@gmail.com>
To: linux-arm-kernel@lists.infradead.org,
linux-omap <linux-omap@vger.kernel.org>
Subject: cpufreq on PandaBoard
Date: Tue, 19 Nov 2013 09:59:07 -0500 [thread overview]
Message-ID: <87eh6ca150.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
Booting a PandaBoard with a recent kernel and devicetree appears to be a
rather messy process. There are dozens of devicetree-related warnings
spewed on boot (many pertaining to missing regulators). At the moment,
however, I'm most interested in this,
cpufreq-cpu0 cpufreq-cpu0.0: no of_node; not parsing pinctrl DT
cpu cpu0: dummy supplies not allowed
cpufreq_cpu0: failed to get cpu0 regulator: -19
cpufreq_cpu0: failed to get cpu0 clock: -2
cpufreq-cpu0: probe of cpufreq-cpu0.0 failed with error -2
What is the status of cpufreq on the PandaBoard? Is this expected to
work?
More generally, if one wants a fairly recent kernel supporting the
PandaBoard's hardware what kernel tree should be used? Is mainline not
yet appropriate? Is linux-next preferred? Perhaps a ti-maintained tree?
Cheers,
- Ben
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: bgamari.foss@gmail.com (Ben Gamari)
To: linux-arm-kernel@lists.infradead.org
Subject: cpufreq on PandaBoard
Date: Tue, 19 Nov 2013 09:59:07 -0500 [thread overview]
Message-ID: <87eh6ca150.fsf@gmail.com> (raw)
Booting a PandaBoard with a recent kernel and devicetree appears to be a
rather messy process. There are dozens of devicetree-related warnings
spewed on boot (many pertaining to missing regulators). At the moment,
however, I'm most interested in this,
cpufreq-cpu0 cpufreq-cpu0.0: no of_node; not parsing pinctrl DT
cpu cpu0: dummy supplies not allowed
cpufreq_cpu0: failed to get cpu0 regulator: -19
cpufreq_cpu0: failed to get cpu0 clock: -2
cpufreq-cpu0: probe of cpufreq-cpu0.0 failed with error -2
What is the status of cpufreq on the PandaBoard? Is this expected to
work?
More generally, if one wants a fairly recent kernel supporting the
PandaBoard's hardware what kernel tree should be used? Is mainline not
yet appropriate? Is linux-next preferred? Perhaps a ti-maintained tree?
Cheers,
- Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131119/97cdc213/attachment.sig>
next reply other threads:[~2013-11-19 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 14:59 Ben Gamari [this message]
2013-11-19 14:59 ` cpufreq on PandaBoard Ben Gamari
2013-11-19 15:01 ` Nishanth Menon
2013-11-19 15:01 ` Nishanth Menon
2013-11-19 17:18 ` Ben Gamari
2013-11-19 17:18 ` Ben Gamari
2013-11-19 17:30 ` Nishanth Menon
2013-11-19 17:30 ` Nishanth Menon
2013-11-19 17:51 ` Ben Gamari
2013-11-19 17:51 ` Ben Gamari
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=87eh6ca150.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 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.