From: "Ron Bianco" <ronb@junction.net>
To: "Ralph Blach" <rcblach@raleigh.ibm.com>
Cc: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Wait queue question
Date: Wed, 14 Feb 2001 10:34:04 -0800 [thread overview]
Message-ID: <000201c096b4$b511dba0$4d012ac7@warp-speed> (raw)
In-Reply-To: <3A8A9EB2.660A7A2D@raleigh.ibm.com>
Hi Ralph, perhaps you could not attach your .vcf files anymore?
If your driver implements non-blocking read() and write() functions, then you don't
have to sleep.
Else others have commented on the alternative to sleep_on().
For non-blocking:
Just use poll_wait() in your poll() function and wakeup_interruptible when there data
available on your Qs.
Then user program's select() and poll() system calls will work properly.
Ron
> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of Ralph
> Blach
> Sent: Wednesday, February 14, 2001 7:05 AM
> To: Embedded Linux list
> Subject: Wait queue question
>
>
> If I have a wait queue thats I am using to wake up a device driver read
> from an interrupt service routine.
> If I get three interrupt and three wake_up_interrables, will I need to
> execute three sleep_ons to get the wait queue back to the null state, or
> is it just back after the first sleep_on?
>
> Chip
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-14 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 15:05 Wait queue question Ralph Blach
2001-02-14 17:30 ` Roland Dreier
2001-02-15 13:59 ` Ralph Blach
2001-02-15 16:39 ` Roland Dreier
2001-02-14 18:34 ` Ron Bianco [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-14 18:04 Ian Abbott
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='000201c096b4$b511dba0$4d012ac7@warp-speed' \
--to=ronb@junction.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rcblach@raleigh.ibm.com \
/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