From: nm@ti•com (Nishanth Menon)
To: linux-arm-kernel@lists•infradead.org
Subject: cpufreq on PandaBoard
Date: Tue, 19 Nov 2013 09:01:53 -0600 [thread overview]
Message-ID: <528B7D61.5020206@ti.com> (raw)
In-Reply-To: <87eh6ca150.fsf@gmail.com>
On 11/19/2013 08:59 AM, Ben Gamari wrote:
>
> 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?
for upstream: Wait for the clock nodes to get merged.. we are at v9 of
discussion thread here[1].
for ti-maintained tree, you need to talk to TI support folks for
appropriate kernel for your product line.
[1] http://marc.info/?t=138271672500002&r=1&w=2
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-11-19 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 14:59 cpufreq on PandaBoard Ben Gamari
2013-11-19 15:01 ` Nishanth Menon [this message]
2013-11-19 17:18 ` Ben Gamari
2013-11-19 17:30 ` Nishanth Menon
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=528B7D61.5020206@ti.com \
--to=nm@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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