linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: problem with queue_task() and mark_bh()...
Date: Thu, 15 Apr 2004 10:08:25 +0200	[thread overview]
Message-ID: <407E42F9.1060201@imc-berlin.de> (raw)
In-Reply-To: <407BF458.5080408@imc-berlin.de>


Hi,

I wrote:

> I have a problem with queue_task() and mark_bh().
> ...
> 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.

When I call run_task_queue(&tq_immediate) right after mark_bh(IMMEDIATE_BH)
then it works.

But I though "run_task_queue(&tq_immediate)" gets called by the kernel
(after every timer interrupt)...


--
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/

  reply	other threads:[~2004-04-15  8:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 14:08 problem with queue_task() and mark_bh() Steven Scholz
2004-04-15  8:08 ` Steven Scholz [this message]
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=407E42F9.1060201@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 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 NNTP newsgroup(s).