From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: PXA27x: CPUFREQ: Don't use fastbus mode
Date: Mon, 11 Apr 2011 15:46:43 +0200 [thread overview]
Message-ID: <20110411134642.GA1519@ucw.cz> (raw)
In-Reply-To: <4D8EFEC1.7010803@compulab.co.il>
Hi!
> >>> 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.
>
> Possibly, but Z2 is not the only one using PXA27x.
> And of course you lose performance, unless you don't care,
> because if it does not work at all, you don't care about performance,
> but again it is wrong to force all PXA27x based boards to this.
Well, some other pxa27x machcines (spitz) are crashing randomly for
_years_ now... so maybe the problem is more widespread?
How easy is to trigger the problem? Do you have script?
Is it possible that this bug triggers with governor==performance.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2011-04-11 13:46 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
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 [this message]
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=20110411134642.GA1519@ucw.cz \
--to=pavel@ucw.cz \
--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).