public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Savin Zlobec <savin@elatec.si>
Cc: ukindler@htwm.de, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re:  CYGACC_CALL_IF_DELAY_US(1000000) fails
Date: Tue, 25 Nov 2003 14:56:00 -0000	[thread overview]
Message-ID: <1069772170.22988.1496.camel@hermes> (raw)
In-Reply-To: <3FC367DF.60104@elatec.si>

On Tue, 2003-11-25 at 07:31, Savin Zlobec wrote:
> Uwe Kindler wrote:
> 
> >Hello,
> >
> >if I call  CYGACC_CALL_IF_DELAY_US(1000000) in order to delay one second,
> >then this call returns a lot
> >faster then 1 second. When I debug the code, then I can see, that
> >HAL_DELAY_US provided by the HAL
> >is only used if no kernel package is included. HAL_DELAY_US(1000000) works
> >fine.
> >
> >If the kernel package is included, the the following calculation takes
> >place:
> >
> >// How many ticks total we should wait for.
> >        usec_ticks = usecs*CYGNUM_KERNEL_COUNTERS_RTC_PERIOD;
> >  
> >
> This is already fixed in CVS.
> 
> PS:
> 
> There are better ways to wait for 1 second if you are using the kernel -
> CYGACC_CALL_IF_DELAY_US is a busy wait.

Indeed - first of all, CYGACC_CALL_IF_DELAY_US should really only be 
used for "short" periods.  Often devices may have requirements like
"the reset pulse should be true for 25us" or whatever.  In this case,
the busy wait code (DELAY_US) is the correct way to go.  

If you have the kernel package (i.e. threads), then use
  cyg_thread_delay(100);  
to wait for one second.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

      reply	other threads:[~2003-11-25 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25 14:28 Savin Zlobec
2003-11-25 14:56 ` Gary Thomas [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=1069772170.22988.1496.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=savin@elatec.si \
    --cc=ukindler@htwm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).