From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: PXA27x: CPUFREQ: Don't use fastbus mode
Date: Sun, 27 Mar 2011 10:28:56 +0300 [thread overview]
Message-ID: <201103271028.56672.anarsoul@gmail.com> (raw)
In-Reply-To: <201103270152.45581.marek.vasut@gmail.com>
On Sunday 27 March 2011 03:52:45 Marek Vasut wrote:
> On Saturday 26 March 2011 20:51:43 Vasily Khoruzhick wrote:
> > PXA27x does not like fastbus for some reason, it can hang in
> > random places when it's enabled. So don't use it to make cpufreq
> > stable.
>
> This is B/S, you're loosing performance!
I'm losing nothing, without this patch cpufreq does not work stable at all on
Zipit Z2.
> I'd suggest module parameter or
> device- specific callback to toggle use of fastbus on/off.
Can you test cpufreq without this patch on pxa270-based board with ondemand or
conservative governor (or userspace with 104/208/312mhz)? Is it stable? If not
then there's no reason to leave fastbus. Btw, pxa25x table has fastbit unset
for some reason. Maybe there's some unknown errata about fastbus bit (same as
half turbo?)
Regards
Vasily
next prev parent reply other threads:[~2011-03-27 7:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 19:51 [PATCH RFC] ARM: PXA27x: CPUFREQ: Don't use fastbus mode Vasily Khoruzhick
2011-03-27 0:52 ` Marek Vasut
2011-03-27 7:28 ` Vasily Khoruzhick [this message]
2011-03-27 9:09 ` Igor Grinberg
2011-03-27 9:48 ` Vasily Khoruzhick
2011-03-27 10:09 ` Igor Grinberg
2011-03-27 14:45 ` Vasily Khoruzhick
2011-03-27 14:50 ` Marek Vasut
2011-03-27 14:56 ` Vasily Khoruzhick
2011-03-27 15:34 ` Marek Vasut
2011-03-27 16:56 ` Robert Jarzmik
2011-03-27 17:13 ` Vasily Khoruzhick
2011-03-28 8:22 ` Igor Grinberg
2011-04-11 13:46 ` Pavel Machek
2011-04-11 20:11 ` Vasily Khoruzhick
2011-04-12 5:22 ` Marek Vasut
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=201103271028.56672.anarsoul@gmail.com \
--to=anarsoul@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).