linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: A problem with shared interrupts
Date: Fri, 27 Jul 2007 00:42:27 +0200	[thread overview]
Message-ID: <200707270042.27917.mb@bu3sch.de> (raw)
In-Reply-To: <46a90082./TQABjOfVYW1o6lY%Larry.Finger@lwfinger.net>

On Thursday 26 July 2007 22:13:54 Larry Finger wrote:
> Michael,
> 
> When I try the -mb tree on my old i386 notebook, I get an "irq 11: nobody cared"
> message and interrupts for the bcm43xx-mac80211 device are not initialized. The
> code in Linville's tree works. The only difference that seems to be important
> is the code returned when a shared interrupt not intended for us is received.
> By making the changes shown below, both trees now work.
> 
> I recall you having a discussion with someone over some aspect of shared IRQ's,
> but I don't remember the details and I'm too busy (lazy) to go back and look.
> 
> Thanks,
> 
> Larry
> ----
> 
> Index: wireless-mb/drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c
> ===================================================================
> --- wireless-mb.orig/drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c
> +++ wireless-mb/drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c
> @@ -1503,7 +1503,7 @@ static void bcm43xx_interrupt_ack(struct
>  /* Interrupt handler top-half */
>  static irqreturn_t bcm43xx_interrupt_handler(int irq, void *dev_id)
>  {
> -	irqreturn_t ret = IRQ_NONE;
> +	irqreturn_t ret = IRQ_HANDLED;
>  	struct bcm43xx_wldev *dev = dev_id;
>  	u32 reason;
>  
> @@ -1517,7 +1517,6 @@ static irqreturn_t bcm43xx_interrupt_han
>  	reason = bcm43xx_read32(dev, BCM43xx_MMIO_GEN_IRQ_REASON);
>  	if (reason == 0xffffffff) /* shared IRQ */
>  		goto out;
> -	ret = IRQ_HANDLED;
>  	reason &= bcm43xx_read32(dev, BCM43xx_MMIO_GEN_IRQ_MASK);
>  	if (!reason)
>  		goto out;
> 
> 

I neither think this is the correct solution, nor do I think that this
is the way bcm43xx-softmac does it. This would always return HANDLED, right?
regardless if the IRQ was for bcm43xx or not. I _do_ think that the bug is
in the driver sharing the IRQ with bcm43xx.

-- 
Greetings Michael.

  reply	other threads:[~2007-07-26 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 20:13 A problem with shared interrupts Larry Finger
2007-07-26 22:42 ` Michael Buesch [this message]
2007-07-27  0:04   ` Larry Finger
2007-07-27  9:54 ` Johannes Berg
2007-07-27 14:36   ` Larry Finger

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=200707270042.27917.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).