linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Stephen Warren" <swarren@wwwdotorg.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Linux Wireless List" <linux-wireless@vger.kernel.org>,
	"Franky Lin" <frankyl@broadcom.com>, "Wei Ni" <wni@nvidia.com>
Subject: Re: [PATCH 07/10] brcmfmac: clear status for in-band interrupt in brcmf_sdbrcm_isr
Date: Sat, 15 Sep 2012 11:19:44 +0200	[thread overview]
Message-ID: <50544830.4020804@broadcom.com> (raw)
In-Reply-To: <5053A74D.6080200@wwwdotorg.org>

On 09/14/2012 11:53 PM, Stephen Warren wrote:
> On 09/13/2012 01:12 PM, Arend van Spriel wrote:
>> From: Franky Lin <frankyl@broadcom.com>
>>
>> SDIO in-band interrupt is level sensitive according to SDIO standard.
>> When the register interrupt handler gets called by SDIO stack it is
>> running in non interrupt context and expected to clear the interrupt
>> from the dongle. Therefore in-band and out-of-band interrupt need to
>> be handled differently.
>
> Tested-by: Stephen Warren <swarren@wwwdotorg.org>
>
> For reference, I took next-20120914, applied this patch series, applied
> a few patches from Wei Ni to set up the SDIO HW on Tegra correctly, and
> tested. The last time I tried this without any patches to the brcmfmac,
> this test caused some system instability issues. This time around, I
> observed no instability. I tested WPA PSK, ping (or flood ping) plus
> playing audio through ALSA.
>
> Is this series likely to make 3.7?
>

Thanks, Stephen

Good to hear. I suspect we are close to the 3.7 merge window, but we do 
hope this will make it mainly for the tegra sdio issue that Wei Ni 
raised. In general the series should resolve issues when used on 
sdhci/mmc framework with in-band interrupt.

Do you still need the patches from Wei Ni and are they SDIO or brcmfmac 
related?

Gr. AvS


  reply	other threads:[~2012-09-15  9:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 19:11 [PATCH 00/10] brcmfmac: sdio dpc restructuring and cleanup Arend van Spriel
2012-09-13 19:11 ` [PATCH 01/10] brcmfmac: absorb brcmf_sendpkt into brcmf_netdev_start_xmit Arend van Spriel
2012-09-13 19:11 ` [PATCH 02/10] brcmfmac: remove obsolete sdio bus sleep mechanism Arend van Spriel
2012-09-13 19:11 ` [PATCH 03/10] brcmfmac: use atomic variable for interrupt pending flag Arend van Spriel
2012-09-13 19:12 ` [PATCH 04/10] brcmfmac: convert SDIO dpc implementation to workqueue Arend van Spriel
2012-09-13 19:12 ` [PATCH 05/10] brcmfmac: streamline SDIO dpc Arend van Spriel
2012-09-13 19:12 ` [PATCH 06/10] brcmfmac: raise SDIO host lock to higher level Arend van Spriel
2012-09-13 19:12 ` [PATCH 07/10] brcmfmac: clear status for in-band interrupt in brcmf_sdbrcm_isr Arend van Spriel
2012-09-14 21:53   ` Stephen Warren
2012-09-15  9:19     ` Arend van Spriel [this message]
2012-09-15 17:12       ` Stephen Warren
2012-09-17 17:37         ` Stephen Warren
2012-09-13 19:12 ` [PATCH 08/10] brcmfmac: fix bug causing errorneous free on exception Arend van Spriel
2012-09-13 19:12 ` [PATCH 09/10] brcmfmac: add parameter check in brcmf_c_mkiovar() Arend van Spriel
2012-09-13 19:12 ` [PATCH 10/10] brcmfmac: simplify handling e-scan result firmware event Arend van Spriel

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=50544830.4020804@broadcom.com \
    --to=arend@broadcom.com \
    --cc=frankyl@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=swarren@wwwdotorg.org \
    --cc=wni@nvidia.com \
    /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).