public inbox for cpufreq@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 58541] New: [pandaboard] cpu frequency limitation
Date: Mon, 20 May 2013 14:31:25 +0000 (UTC)	[thread overview]
Message-ID: <bug-58541-12968@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=58541

           Summary: [pandaboard] cpu frequency limitation
           Product: Power Management
           Version: 2.5
    Kernel Version: 3.9.3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@vger.kernel.org
        ReportedBy: liquid.acid@gmx.net
        Regression: No


Created an attachment (id=102051)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=102051)
dmesg output after boot

Hello,

the ARMv7 in the Pandaboard ES (OMAP4460) should support a maximum frequency of
around 1.2GHz.

However it looks like that it's currently limited to 920MHz.

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:
350000 700000 920000

Even worse:

cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq 
699977

Greets,
Tobias

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2013-05-20 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 14:31 bugzilla-daemon [this message]
2013-05-20 14:33 ` [Bug 58541] [pandaboard] cpu frequency limitation bugzilla-daemon
2013-05-20 19:48 ` bugzilla-daemon
2013-05-20 19:49 ` bugzilla-daemon
2013-05-20 20:58 ` bugzilla-daemon
2013-05-29  2:44 ` bugzilla-daemon

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=bug-58541-12968@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@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