From: bgamari.foss@gmail.com (Ben Gamari)
To: linux-arm-kernel@lists.infradead.org
Subject: cpufreq on PandaBoard
Date: Tue, 19 Nov 2013 12:51:21 -0500 [thread overview]
Message-ID: <87bo1gnuue.fsf@gmail.com> (raw)
In-Reply-To: <528BA031.5050201@ti.com>
Nishanth Menon <nm@ti.com> writes:
> On 11/19/2013 11:18 AM, Ben Gamari wrote:
>>
>> 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.
>
> You are probably picking up a branch that is yet to be posted :)...
> and I assume you know the risk of in-development patches ;)
>
The house hasn't burned down yet... ;)
> - the branch looks to introduce purely clock nodes which patch [2]
> adds on to and makes cpufreq work as a start..
>
Thanks!
>>
>> 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.
>
> We are still at "step 1 - get clock nodes" :(... and no, situation has
> not improved since May 2013 when I originally posted that G+ comment
> (and not because we have not been trying..).
>
Ouch. Good luck!
>> I wasn't asking for official support, just wondering where work is
>> currently happening.
>
> they are happening here in linux-omap mailing list.. just that the
> changes are pretty fundamental and a lot of discussions have been
> taking place
>
Thanks!
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/f655addd/attachment.sig>
prev parent reply other threads:[~2013-11-19 17:51 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
2013-11-19 17:18 ` Ben Gamari
2013-11-19 17:30 ` Nishanth Menon
2013-11-19 17:51 ` Ben Gamari [this message]
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=87bo1gnuue.fsf@gmail.com \
--to=bgamari.foss@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).