From: Mark Jackson <mpfj-list@mimc.co.uk>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: AM335x mpurate + bogomips
Date: Thu, 21 Feb 2013 16:36:15 +0000 [thread overview]
Message-ID: <51264CFF.8050200@mimc.co.uk> (raw)
Before I dig any deeper, can anyone tell me if the bootarg "mpurate" is meant to
be supported for AM335x SoCs ?
I've tried it on our custom board using 3v8, but no joy.
The boot log shows:-
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.8.0-03059-g621553c-dirty (mpfj@mpfj-nanobone) (gcc version 4.5.4 (Buildroot 2012.11) ) #113 SMP Thu Feb 21 16:29:48 GMT 2013
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: Newflow NanoBone
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] CPU: All CPU(s) started in SVC mode.
[ 0.000000] AM335X ES1.0 (neon )
...
[ 0.000000] Kernel command line: console=ttyO0,115200n8 mpurate=720 root=/dev/mmcblk0p2 ro rootfstype=ext2 rootwait
...
[ 0.001119] Calibrating delay loop... 364.48 BogoMIPS (lpj=1425408)
I have seen other boot logs outputs [1] from other people where they are getting nearly double that.
Looking at omap2xxx_clk_arch_init(), only ompa24xx devices are supported.
Am I missing something obvious (like it's not yet supported !!) ?
Cheers
Mark J.
[1] http://e2e.ti.com/support/embedded/linux/f/354/t/245316.aspx
next reply other threads:[~2013-02-21 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 16:36 Mark Jackson [this message]
2013-02-21 18:30 ` AM335x mpurate + bogomips Hiremath, Vaibhav
2013-02-22 8:03 ` Jason Kridner
2013-02-22 14:49 ` Nishanth Menon
2013-02-22 16:43 ` Frank Agius
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=51264CFF.8050200@mimc.co.uk \
--to=mpfj-list@mimc.co.uk \
--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