From: Mohan <mohanv@aftek.com>
To: linux-kernel@vger.kernel.org
Subject: wait queue sharing..
Date: Fri, 11 Mar 2005 17:11:18 +0530 [thread overview]
Message-ID: <423183DE.3020102@aftek.com> (raw)
Hello All,
I have a question regarding the wait queues. I have a driver
pxausb_core.o which is the core driver which does all USB endpoint
handling and hardware interaction. I have one more driver on top of it
usb-serial which provides for the user-level interaction(like read,
write, ioctl).
I have implemented a blocking ioctl, which sends events about the state
of USB device(enumerated, suspended, disconnected, etc).
For this ioctl, i have declared a wait_queue and initialized (using
init_waitqueue_head() func.) in the usb_ctl.c which is part of
pxausb_core.o. (it has usb_send.c, usb_recv.c, usb_ctl.c, usb_ep0.c).
I am using that wait_queue variable in usb-ser.c.
I just wanted to clarify myself whether the wait queues can be shared
between two driver modules.
Thank you...
regards,
mohan
next reply other threads:[~2005-03-11 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 11:41 Mohan [this message]
2005-03-12 18:53 ` wait queue sharing Kedar Sovani
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=423183DE.3020102@aftek.com \
--to=mohanv@aftek.com \
--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