From: Ben Gamari <bgamari.foss@gmail.com>
To: Nishanth Menon <nm@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: cpufreq on PandaBoard
Date: Tue, 19 Nov 2013 12:18:14 -0500 [thread overview]
Message-ID: <87hab8nwdl.fsf@gmail.com> (raw)
In-Reply-To: <528B7D61.5020206@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
Nishanth Menon <nm@ti.com> writes:
> 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].
>
I take it that the clock node work does not itself fix cpufreq? I've
built the 3.12-dt-clks-v10-dev branch. On the bright side, it boots and
appears to run just fine. Unfortunately, there isn't even a mention of
cpufreq in the boot log.
I've seen your Google+ post[1] from May enumerating the steps to having
working DVFS. It would be useful to post an update showing what has been
merged, what is waiting for merge, and what is still in progress.
> for ti-maintained tree, you need to talk to TI support folks for
> appropriate kernel for your product line.
>
I wasn't asking for official support, just wondering where work is
currently happening.
Thanks for your help.
Cheers,
- Ben
[1] https://plus.google.com/112464029509057661457/posts/gvyZQcNieoq
[-- 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 12:18:14 -0500 [thread overview]
Message-ID: <87hab8nwdl.fsf@gmail.com> (raw)
In-Reply-To: <528B7D61.5020206@ti.com>
Nishanth Menon <nm@ti.com> writes:
> 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].
>
I take it that the clock node work does not itself fix cpufreq? I've
built the 3.12-dt-clks-v10-dev branch. On the bright side, it boots and
appears to run just fine. Unfortunately, there isn't even a mention of
cpufreq in the boot log.
I've seen your Google+ post[1] from May enumerating the steps to having
working DVFS. It would be useful to post an update showing what has been
merged, what is waiting for merge, and what is still in progress.
> for ti-maintained tree, you need to talk to TI support folks for
> appropriate kernel for your product line.
>
I wasn't asking for official support, just wondering where work is
currently happening.
Thanks for your help.
Cheers,
- Ben
[1] https://plus.google.com/112464029509057661457/posts/gvyZQcNieoq
-------------- 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/7e86274a/attachment.sig>
next prev parent reply other threads:[~2013-11-19 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 14:59 cpufreq on PandaBoard Ben Gamari
2013-11-19 14:59 ` Ben Gamari
2013-11-19 15:01 ` Nishanth Menon
2013-11-19 15:01 ` Nishanth Menon
2013-11-19 17:18 ` Ben Gamari [this message]
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=87hab8nwdl.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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.