linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 05/10] mmp: fix clock tick rate in mmp2
Date: Wed, 28 Apr 2010 20:26:46 +0800	[thread overview]
Message-ID: <z2hf17812d71004280526u6b6171a0rb0c47be480616b1@mail.gmail.com> (raw)
In-Reply-To: <p2i771cded01004280520wc663c42bva8c270fbdfaf4ddc@mail.gmail.com>

On Wed, Apr 28, 2010 at 8:20 PM, Haojian Zhuang
<haojian.zhuang@gmail.com> wrote:
> From 4d3bcaf4bd83886fe5d14be22bbc4baf2d51a543 Mon Sep 17 00:00:00 2001
> From: Mingliang Hu <mhu4@marvell.com>
> Date: Mon, 12 Apr 2010 17:55:21 +0800
> Subject: [PATCH] [ARM] mmp: fix clock tick rate in mmp2
>
> In MMP2, clock tick rate should be 6500000.
>
> Signed-off-by: Mingliang Hu <mhu4@marvell.com>
> Signed-off-by: Haojian Zhuang <haojian.zhuang@marvell.com>
> ---
> ?arch/arm/mach-mmp/include/mach/timex.h | ? ?4 ++++
> ?1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-mmp/include/mach/timex.h
> b/arch/arm/mach-mmp/include/mach/timex.h
> index 6cebbd0..70c9f1d 100644
> --- a/arch/arm/mach-mmp/include/mach/timex.h
> +++ b/arch/arm/mach-mmp/include/mach/timex.h
> @@ -6,4 +6,8 @@
> ?* published by the Free Software Foundation.
> ?*/
>
> +#ifdef CONFIG_CPU_MMP2
> +#define CLOCK_TICK_RATE ? ? ? ? ? ? ? ?6500000
> +#else

Actually we no longer depend on this macro, yet it's straightforward to
keep it here without side effect. So OK.

> ?#define CLOCK_TICK_RATE ? ? ? ? ? ? ? ?3250000
> +#endif
> --
> 1.5.6.5
>

  reply	other threads:[~2010-04-28 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 12:20 [PATCH 05/10] mmp: fix clock tick rate in mmp2 Haojian Zhuang
2010-04-28 12:26 ` Eric Miao [this message]
2010-04-28 13:01   ` Eric Miao

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=z2hf17812d71004280526u6b6171a0rb0c47be480616b1@mail.gmail.com \
    --to=eric.y.miao@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).