From: Tony Lindgren <tony@atomide.com>
To: Maximilian Schwerin <Maximilian.Schwerin@tigris.de>
Cc: linux-omap@vger.kernel.org
Subject: Re: Beagleboard xM crashes when being set to 800MHz with smartreflex on linux-omap-3.6-rc6
Date: Fri, 21 Sep 2012 12:16:30 -0700 [thread overview]
Message-ID: <20120921191629.GH28835@atomide.com> (raw)
In-Reply-To: <5448984682E7954C9BFF27F747A9C6CA56E38E@dolphin.TIGRIS.local>
* Maximilian Schwerin <Maximilian.Schwerin@tigris.de> [120920 23:46]:
> Hi,
>
> I've just built a linux-omap kernel at 3.6-rc6 using omap2plus_defconfig
> as basis for the kernel config.
>
> When I enable smartreflex and switch to 800MHz via
>
> echo 1 > /sys/kernel/debug/smartreflex/smartreflex_core/autocomp
> echo 1 > /sys/kernel/debug/smartreflex/smartreflex_mpu_iva/autocomp
> cpufreq-set -f 800MHz
>
> the board crashes. If I switch to 800MHz and enable smartreflex later
> nothing happens. This used to work in my 3.3 based kernel.
I'm suspecting that this is because of all the missing PM
errata we don't have in the mainline kernel :(
I think we're missing at least the following based on a quick grep
of the Nokia patched PM code:
- 3430 (and 3630?) hs omap cs1 off-idle bug where save/restore needs to be in lowmem
- 3630 retention idle is missing errata handling for 1.85/i581
- 3630 off idle is missing 1.87 handling
- smartreflex missing twl4030 errata?
- Nokia patched PM code mentions also quite a few other missing
errata such as 1.88, 1.142, i582, i467, i468, 1.164
This may be a bit out of date as it's based on some notes I made
few months ago after I started noticing flakeyness on my 3630 zoom3
board.
Regards,
Tony
next prev parent reply other threads:[~2012-09-21 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 6:45 Beagleboard xM crashes when being set to 800MHz with smartreflex on linux-omap-3.6-rc6 Maximilian Schwerin
2012-09-21 8:34 ` Joni Lapilainen
2012-09-21 12:52 ` Robert Nelson
2012-09-21 19:16 ` Tony Lindgren [this message]
2012-10-02 0:00 ` Kevin Hilman
2012-10-08 8:50 ` AW: " Maximilian Schwerin
2012-10-10 10:49 ` jean-philippe francois
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=20120921191629.GH28835@atomide.com \
--to=tony@atomide.com \
--cc=Maximilian.Schwerin@tigris.de \
--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.