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: bcm43xx-mac80211: a fix for the shared interrupt problem
Date: Sat, 28 Jul 2007 18:48:02 +0200	[thread overview]
Message-ID: <200707281848.02554.mb@bu3sch.de> (raw)
In-Reply-To: <46aab9a4.pmEWFfaWaaFDLvZd%Larry.Finger@lwfinger.net>

On Saturday 28 July 2007 05:36:04 Larry Finger wrote:
> Michael,
> 
> I was in the right area with my previous fix to the "irq 11: nobody cared"
> message. I think for shared interrupts, skipping out if the status is not
> BCM43xx_STAT_STARTED is too severe. I added a message printing out the status
> whenever it skipped out, and found many thousands of interrupts with the
> status equal to BCM43xx_STAT_INITIALIZED. The patch below makes the necessary
> change and modifies a couple of asserts that depend on it.
> 
> This patch has been tested on BCM4306 and BCM4318 with shared interrupts,
> and BCM4311 without.
> 
> Thanks,
> 
> Larry
> ----
> 
> 
> Index: wireless-mb/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c
> ===================================================================
> --- wireless-mb.orig/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c
> +++ wireless-mb/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c
> @@ -1374,7 +1374,7 @@ static void bcm43xx_interrupt_tasklet(st
>  
>  	spin_lock_irqsave(&dev->wl->irq_lock, flags);
>  
> -	assert(bcm43xx_status(dev) == BCM43xx_STAT_STARTED);
> +	assert(bcm43xx_status(dev) >= BCM43xx_STAT_INITIALIZED);
>  
>  	reason = dev->irq_reason;
>  	for (i = 0; i < ARRAY_SIZE(dma_reason); i++) {
> @@ -1512,7 +1512,7 @@ static irqreturn_t bcm43xx_interrupt_han
>  
>  	spin_lock(&dev->wl->irq_lock);
>  
> -	if (bcm43xx_status(dev) < BCM43xx_STAT_STARTED)
> +	if (bcm43xx_status(dev) < BCM43xx_STAT_INITIALIZED)
>  		goto out;
>  	reason = bcm43xx_read32(dev, BCM43xx_MMIO_GEN_IRQ_REASON);
>  	if (reason == 0xffffffff) /* shared IRQ */
> @@ -1522,7 +1522,7 @@ static irqreturn_t bcm43xx_interrupt_han
>  	if (!reason)
>  		goto out;
>  
> -	assert(bcm43xx_status(dev) == BCM43xx_STAT_STARTED);
> +	assert(bcm43xx_status(dev) >= BCM43xx_STAT_INITIALIZED);
>  
>  	dev->dma_reason[0] = bcm43xx_read32(dev, BCM43xx_MMIO_DMA0_REASON)
>  			     & 0x0001DC00;
> 
> 

That's not the right bugfix.
If the interface is not STAT_STARTED, it should _not_ generate IRQs.
The bug is elsewhere in the init routines.
Please find out which IRQ bits are generated for these spurious IRQs.

-- 
Greetings Michael.

  reply	other threads:[~2007-07-28 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-28  3:36 bcm43xx-mac80211: a fix for the shared interrupt problem Larry Finger
2007-07-28 16:48 ` Michael Buesch [this message]
2007-07-28 20:53   ` Larry Finger
2007-07-28 23:03     ` Michael Buesch
2007-07-28 23:58       ` Larry Finger
2007-07-29  8:54         ` Michael Buesch

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=200707281848.02554.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).