mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Wjatscheslaw Stoljarski (Slawa)" <wjatscheslaw.stoljarski@kiwigrid.com>
To: barebox@lists.infradead.org
Subject: [PATCH] ARM i.MX53: notify clocksource about changing clock
Date: Tue, 24 Jul 2012 15:50:08 +0200	[thread overview]
Message-ID: <500EA810.3050902@kiwigrid.com> (raw)

This fix a clock inaccuracy in get_time_ns (used by sleep, time, etc).

At i.MX53 power-on GPT clock is typically 55500000 Hz, and it will be used
to calc the clock multiplier. After call imx53_init_lowlevel() GPT clock 
will
changed (e.g. to 66666666 Hz), but multiplier not. To fix this behavior call
clock_notifier_call_chain() after changing clock in imx53_init_lowlevel().

Signed-off-by: Wjatscheslaw Stoljarski 
<wjatscheslaw.stoljarski@kiwigrid.com>
---
  arch/arm/mach-imx/imx53.c |    3 +++
  1 file changed, 3 insertions(+)

diff --git a/arch/arm/mach-imx/imx53.c b/arch/arm/mach-imx/imx53.c
index e20b60a..3359819 100644
--- a/arch/arm/mach-imx/imx53.c
+++ b/arch/arm/mach-imx/imx53.c
@@ -18,6 +18,7 @@
  #include <init.h>
  #include <common.h>
  #include <io.h>
+#include <notifier.h>
  #include <sizes.h>
  #include <mach/imx5.h>
  #include <mach/imx-regs.h>
@@ -211,4 +212,6 @@ void imx53_init_lowlevel(unsigned int cpufreq_mhz)
  	writel(0xffffffff, ccm + MX53_CCM_CCGR7);
   	writel(0, ccm + MX5_CCM_CCDR);
+
+	clock_notifier_call_chain();
  }
-- 
1.7.9.5


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-07-24 13:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 13:50 Wjatscheslaw Stoljarski (Slawa) [this message]
2012-07-25  6:42 ` Sascha Hauer

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=500EA810.3050902@kiwigrid.com \
    --to=wjatscheslaw.stoljarski@kiwigrid.com \
    --cc=barebox@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