From: Ralf Baechle <ralf@linux-mips.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Alchemy: work around clock misdetection on early Au1000 (take 2)
Date: Thu, 27 Mar 2008 13:37:54 +0000 [thread overview]
Message-ID: <20080327133754.GB19381@linux-mips.org> (raw)
In-Reply-To: <200803271609.31772.sshtylyov@ru.mvista.com>
On Thu, Mar 27, 2008 at 04:09:31PM +0300, Sergei Shtylyov wrote:
> Work around the CPU clock miscalculation on Au1000DA/HA/HB due the sys_cpupll
> register being write-only, i.e. actually do what the comment before cal_r4off()
> function advertised for years but the code failed at. This is achieved by just
> giving user a chance to define the clock explicitly in the board config. via
> CONFIG_SOC_AU1000_FREQUENCY option, defaulting to 396 MHz if the option is not
> given...
>
> The patch is based on the AMD's big unpublished patch, the issue seems to be an
> undocumented errata (or feature :-)...
Applied, thanks,
Ralf
prev parent reply other threads:[~2008-03-27 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 13:09 [PATCH] Alchemy: work around clock misdetection on early Au1000 (take 2) Sergei Shtylyov
2008-03-27 13:17 ` Sergei Shtylyov
2008-03-27 13:34 ` Ralf Baechle
2008-03-27 13:37 ` Ralf Baechle [this message]
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=20080327133754.GB19381@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=sshtylyov@ru.mvista.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