mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Daniel Schultz <d.schultz@phytec.de>
To: "Jan Lübbe" <jlu@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 2/2] ARM: am335x: Changed timer
Date: Fri, 17 Jul 2015 15:44:49 +0200	[thread overview]
Message-ID: <55A906D1.3040901@phytec.de> (raw)
In-Reply-To: <1437124574.3498.73.camel@pengutronix.de>

Am 17.07.2015 um 11:16 schrieb Jan Lübbe:
> On Do, 2015-07-16 at 10:51 +0200, Daniel Schultz wrote:
>> The dmtimer0 is too inaccurate to be used for measurements.
>> We switch to the more accurate dmtimer2.
>
> What are you trying to measure? Is the resolution or the accuracy too
> low?
While testing with dhrystone on our boards, I figured out that the 
timestamps from dmtimer0 run 20% too quick.

You can also make a quick test on a am335x board with
sleep 10

You will notice that the sleep only takes 8 seconds. This quite too 
inaccurate.

>
>> +#define CLK_M_OSC	25000000
>
>> +static int dmtimer_init(void)
>> +{
>> +	dmtimer_cs.mult = clocksource_hz2mult(CLK_M_OSC, dmtimer_cs.shift);
>> +	/* Enable counter */
>> +	writel(0x3, base + TCLR);
>> +
>> +	return init_clock(&dmtimer_cs);
>
> You use a fixed M_OSC of 25 MHz, but this value actually depends on the
> the board. The AM335x supports 19.2, 24 and 26 MHz in addition to 25
> MHz.
see new patch.
> The advantage of using dmtimer0 is that it is always available and runs
> at 32KiHz on every board.
>
> Regards,
> Jan
>

Kind regards,
Daniel

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

      reply	other threads:[~2015-07-17 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  8:51 Daniel Schultz
2015-07-17  9:16 ` Jan Lübbe
2015-07-17 13:44   ` Daniel Schultz [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=55A906D1.3040901@phytec.de \
    --to=d.schultz@phytec.de \
    --cc=barebox@lists.infradead.org \
    --cc=jlu@pengutronix.de \
    /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