From: NeilBrown <neilb@suse.de>
To: t-kristo@ti.com
Cc: Kevin Hilman <khilman@ti.com>, linux-omap@vger.kernel.org
Subject: Re: bisected regression: arm: omap3: voltage: fix channel configuration
Date: Wed, 25 Jul 2012 11:47:42 +1000 [thread overview]
Message-ID: <20120725114742.30e25e31@notabene.brown> (raw)
In-Reply-To: <1343119876.30247.49.camel@sokoban>
[-- Attachment #1: Type: text/plain, Size: 2598 bytes --]
On Tue, 24 Jul 2012 11:51:16 +0300 Tero Kristo <t-kristo@ti.com> wrote:
> On Tue, 2012-07-24 at 17:34 +1000, NeilBrown wrote:
> > On Tue, 24 Jul 2012 09:28:24 +0300 Tero Kristo <t-kristo@ti.com> wrote:
> >
> > > On Tue, 2012-07-24 at 11:30 +1000, NeilBrown wrote:
> >
> > > > Might there be some way to get it to scale higher than 600MHz?
> > > > The first message from U-boot says:
> > > >
> > > > OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
> > > >
> > > > and the board manufacturer thinks it should be capable of 800MHz.
> > >
> > > You need to enable 800MHz OPP similarly to what is done in
> > > beagle_opp_init() in board-omap3beagle.c. I am not sure what your board
> > > is detected as, depends on your boot loader (check /proc/cpuinfo.)
> >
> > Thanks!
> > Yes, my board identifies as cpu_is_omap3630() so that code looks relevant.
> > I copied the opp_init across to my board file, it runs without complaining
> > but it now gets to
> >
> > [ ok ] Loading cpufreq kernel modules...done (none).
> > [....] CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...
> >
> >
> > and hangs. magic SYSRQ doesn't respond.
> >
> > Any hints?
>
> You only enabled opp for 800MHz right? I am just wondering if the
> voltage levels for mpu / core opps are correct for your board... You may
> want to check the opp tables against the information provided by your
> board manufacturer. The trace about cpufreq enabling ondemand governor
> indicates it is switching to frequency throttling mode at that point, so
> it most likely tries to raise MPU frequency to 800MHz (CPU load is
> pretty high during boot.) You can try adding some trace to cpufreq
> driver itself to see what is happening.
Yes, just 800MHz. I just copied the code from board-omap3beagle.c, so
it is actually 800MHz for MPU and 660MHz for IVA.
I tried running with that and with your patch reverted and it works
perfectly. I even get 33% better speed on CPU-intensive workloads, so it
really is running at 800MHz.
>
> Another thing to verify would be to check the voltage rails on your
> board schematics to see how the supply voltages are delivered.
I have a basic understanding of the schematics, but I don't really know what
to look for when it comes to power routing.
If you happen to have time and interest, the schematics are in the manual
that can be downloaded from
http://projects.goldelico.com/p/gta04-main/downloads/
I've got the GTA04A3, so GTA04A3-1-complete.pdf is the one you want.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-07-25 1:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 11:06 bisected regression: arm: omap3: voltage: fix channel configuration NeilBrown
2012-07-23 14:24 ` Tero Kristo
2012-07-24 1:30 ` NeilBrown
2012-07-24 6:28 ` Tero Kristo
2012-07-24 7:34 ` NeilBrown
2012-07-24 8:51 ` Tero Kristo
2012-07-25 1:47 ` NeilBrown [this message]
2012-07-25 7:52 ` Tero Kristo
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=20120725114742.30e25e31@notabene.brown \
--to=neilb@suse.de \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=t-kristo@ti.com \
/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