From: Scott Wood <scottwood@freescale.com>
To: Alan Bennett <embedded@akb.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Timers on mpc8248 etc...
Date: Wed, 28 Nov 2007 17:43:17 -0600 [thread overview]
Message-ID: <474DFD15.603@freescale.com> (raw)
In-Reply-To: <bfa0697f0711281541l31225d59ne78c8fe40286052e@mail.gmail.com>
Alan Bennett wrote:
> I've got a routine that needs to delay for X microseconds, this is a
> must. The command after schedule_timeout must has to wait for the HW
> to complete a task that takes X microseconds.
>
> I would think that one way to do this is with a simple
> schedule_timeout. But in the example below, the time that passes from
> run1() to dontrun() is far less than 3.2 msecs. Infact, sometimes its
> ~ 800 micros according the a analyzer looking at points triggered in
> run1() and donrun(). Could this be a configuration problem with the
> timer/interrupt that generates the jiffies?
Are you sure the timebase frequency is set correctly in the device tree?
-Scott
next prev parent reply other threads:[~2007-11-28 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 23:41 Timers on mpc8248 etc Alan Bennett
2007-11-28 23:43 ` Scott Wood [this message]
2007-11-29 4:06 ` Alan Bennett
2007-11-29 11:31 ` Vitaly Bordug
2007-11-29 13:50 ` Alan Bennett
2007-11-29 19:05 ` Alan Bennett
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=474DFD15.603@freescale.com \
--to=scottwood@freescale.com \
--cc=embedded@akb.net \
--cc=linuxppc-dev@ozlabs.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).