From: Bill Davidsen <davidsen@tmr.com>
To: Mockern@yandex.ru
Cc: hjk@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: Question: 20 microseconds delay
Date: Sat, 03 Mar 2007 16:02:50 -0500 [thread overview]
Message-ID: <45E9E27A.5010403@tmr.com> (raw)
In-Reply-To: <45E98A79.000001.09982@colgate.yandex.ru>
Mockern wrote:
> The problem is that I need to use wait_event_timeout function
AFAIK you can't do that, it's just not the right tool for the job. You
can always use a single jiffy and be sure you will wait at least 20us,
or use usleep.
No matter how much you "need to use" your snowblower, it won't mow your
lawn.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
prev parent reply other threads:[~2007-03-03 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 14:20 Question: 20 microseconds delay Mockern
2007-03-03 14:32 ` Jiri Slaby
2007-03-03 14:46 ` Mockern
2007-03-03 14:52 ` Jiri Slaby
2007-03-03 14:33 ` Hans-Jürgen Koch
2007-03-03 14:47 ` Mockern
2007-03-03 21:02 ` Bill Davidsen [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=45E9E27A.5010403@tmr.com \
--to=davidsen@tmr.com \
--cc=Mockern@yandex.ru \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.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