From: Vishwanath Sripathy <vishwanath.bs@ti.com>
To: javier Martin <javier.martin@vista-silicon.com>,
linux-omap@vger.kernel.org
Subject: RE: cpufreq support for the Beagleboard.
Date: Mon, 21 Mar 2011 16:27:44 +0530 [thread overview]
Message-ID: <641332d61bd84a5de4483dbb496ecd5a@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=mWbpi7i6if5TdBCoi0bUFGWcxOba1kZ+6EePa@mail.gmail.com>
Cpufreq for omap is not mainlined yet.
Patches for supporting omap cpufreq are posted at
https://patchwork.kernel.org/patch/495021/
Same are available at
git://gitorious.org/omap-pm/linux.git omap_dvfs
Vishwa
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of javier Martin
> Sent: Monday, March 21, 2011 4:12 PM
> To: linux-omap@vger.kernel.org
> Subject: cpufreq support for the Beagleboard.
>
> Hi,
> I am testing latest 2.6.38 stable kernel with my Beagleboard xM. I
> have enabled CONFIG_CPU_FREQ option and several governors.
> However, when I boot the board and execute "cpufreq-info" I get the
> following:
>
> root@beagleboard:~# cpufreq-info
> cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
> Report errors and bugs to cpufreq@vger.kernel.org, please.
> analyzing CPU 0:
> no or unknown cpufreq driver is active on this CPU
> maximum transition latency: 0.00 ms.
>
> I've read some information in this wiki:
> http://elinux.org/OMAP_Power_Management
>
> It seems that cpufreq is still not in mainline but it should be
> already on pm branch of omap repository. However, I've also tried
> compiling this one and I've got the same problem.
>
> Could anyone clarify whether cpufreq is supported or not in the
> Beagleboard xM and where?
>
> Thank you.
>
> --
> Javier Martin
> Vista Silicon S.L.
> CDTUC - FASE C - Oficina S-345
> Avda de los Castros s/n
> 39005- Santander. Cantabria. Spain
> +34 942 25 32 60
> www.vista-silicon.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-21 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 10:42 cpufreq support for the Beagleboard javier Martin
2011-03-21 10:57 ` Vishwanath Sripathy [this message]
2011-03-21 12:10 ` javier Martin
2011-03-21 13:24 ` Vishwanath Sripathy
2011-03-21 14:10 ` javier Martin
2011-03-21 15:08 ` Menon, Nishanth
2011-03-21 18:44 ` Matt Johnson
2011-03-22 5:09 ` Vishwanath Sripathy
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=641332d61bd84a5de4483dbb496ecd5a@mail.gmail.com \
--to=vishwanath.bs@ti.com \
--cc=javier.martin@vista-silicon.com \
--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 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).