From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: problem with queue_task() and mark_bh()...
Date: Tue, 13 Apr 2004 16:08:24 +0200 [thread overview]
Message-ID: <407BF458.5080408@imc-berlin.de> (raw)
Hi there,
I have a problem with queue_task() and mark_bh().
In a driver for the wireless HERMES-II chipset I found the code snippets
/* Register the ISR handler information here... */
lp->task.routine = (void (*)(void *))wl_isr_handler;
lp->task.data = lp;
printk("wl_isr_handler is @ %#lx\n", lp->task.routine);
At a later point (namely in the interrupt service rountine this happens:
/* If we have interrupts pending, then put them on a system task queue.*/
if( events == HCF_INT_PENDING ) {
/* Schedule the ISR handler as a bottom-half task in the
* tq_immediate queue
*/
printk( "Schedule the ISR handler %#lx...\n", lp->task.routine);
queue_task( &( lp->task ), &tq_immediate );
mark_bh( IMMEDIATE_BH );
}
The problem is now that the queued task lp->task (i.e. wl_isr_handler) never
get's called! And thus the driver does not work.
If I call the function directly using
lp->task.routine(lp);
instead of queue_task() and mark_bh() the function wl_isr_handler() gets
called and the driver works.
Any idea why queue_task() and mark_bh() do not work as expected?
How could I debug this problem?
(The two printk's show the same address.)
I am using linuxppc-2.4.25 from DENX CVS.
Thanks a million!!!
--
Steven Scholz
imc Measurement & Control imc Meßsysteme GmbH
Voltastr. 5 Voltastr. 5
13355 Berlin 13355 Berlin
Germany Deutschland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-04-13 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 14:08 Steven Scholz [this message]
2004-04-15 8:08 ` problem with queue_task() and mark_bh() Steven Scholz
2004-04-15 11:30 ` Steven Scholz
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=407BF458.5080408@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.