All of lore.kernel.org
 help / color / mirror / Atom feed
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 20:13:19 +0300	[thread overview]
Message-ID: <201103272013.19981.anarsoul@gmail.com> (raw)
In-Reply-To: <87r59sbixx.fsf@free.fr>

On Sunday 27 March 2011 19:56:58 Robert Jarzmik wrote:

> These 2 work well on the mioa701 platform, under the constraint that the
> minimal frequency is set to 208 instead of 104.
> 
> I would think as Marek that it's a under-voltage issue, unless it's the
> 104Mhz transition issue which lasts for as long as I own my platform (and
> which might be mioa701 specific AFAIK).

I tried to disable regulator at all (so, regulator is left in default state), 
stock bootloader configures CPU to 208mhz(normal)/312mhz(fast) and enables 
fast mode, but leaves fastbus disabled. So I tried fixed 208mhz and 312mhz 
with fastbus bit set - it hangs in random places, even without cpu freq 
transitions... So maybe it's some hw misdesign, but once again - it works 
pretty stable @104-416mhz with fastbus disabled.

Regards
Vasily

  reply	other threads:[~2011-03-27 17:13 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 [this message]
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=201103272013.19981.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 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.