All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Barada <peter.barada@gmail.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: cpufreq-info doesn't work in linux-3.0 on DM3730
Date: Sat, 01 Oct 2011 13:32:19 -0400	[thread overview]
Message-ID: <4E874EA3.6060903@gmail.com> (raw)

I'm trying to get frequency scaling working in linux-3.0, and it after 
digging into why cpufreq-info works in 2.6.32 and doesn't in 3.0, I've 
found that omap_cpu_init() returs -ENOENT due to clk_get(NULL, 
"virt_prcm_set") failing.

In the older 2.6.32 kernel it used "arm_fck" for MPU_CLK instead of 
"virt_prcm_set", but that option isn't in the linux-3.0 source (or the 
current source in tony's tree on github.com).  I tried reverting to 
"arm_fck", but on a DM3730 cpupfreq-info only shows 600Mhz as a 
possibility, and none of the other operating points.

Does anyone have CPU frequency scaling working in linux-3.0 and have any 
suggestions on what I'm doing wrong?

-- 
Peter Barada
peter.barada@gmail.com


             reply	other threads:[~2011-10-01 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-01 17:32 Peter Barada [this message]
2011-10-03 22:28 ` cpufreq-info doesn't work in linux-3.0 on DM3730 Kevin Hilman

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=4E874EA3.6060903@gmail.com \
    --to=peter.barada@gmail.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 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.